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

Projects and Resources, depending :slightly_smiling_face: And if there's no context in the conversation, I add "Pulumi".

I used those names the standard locations in the directory structure, too. All the `index.ts` files are in subdirs of _src/main/pulumi/projects/_, and all the reusable subclasses of `ComponentResourse` are in _src/main/pulumi/resources/_.

Overall, I call it “infrastructure code”

I bundled my code in “permission” (IAM stuff), “network” (VPC, subnets, peering), “storage” (disks, blob, (no)sql), “execution” (VMs, K8s, …) &amp; “apps”  (deployments, serverless) libraries (pure NPM packages), which I can then mix &amp; match in Pulumi projects.