No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Also actively in progress.

Import support in <https://github.com/pulumi/pulumi/issues/1662> and <https://github.com/pulumi/pulumi/issues/1635>.  And `alias`s to allow changing the name of a resources in <https://github.com/pulumi/pulumi/issues/458>.

It's possible to manually edit state files to achieve both goals already today, but will be easier once these features land.

One more question on this: would the issues listed above support moving top-level resources from a pulumi program into a <https://pulumi.io/reference/pkg/nodejs/@pulumi/pulumi/#ComponentResource> (e.g. in a reusable npm package)?

Yes - that's one of the key topics raised in and tracked by <https://github.com/pulumi/pulumi/issues/458>.  We believe the "aliases" approach there can be made to support this - but we still have work to do to finish the design of this.