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

We have a blog post that you should find useful on this subject: <https://www.pulumi.com/blog/iac-recommended-practices-structuring-pulumi-projects/>

In general, I would recommend starting simple and evolving your codebase from there. I don't think you'll need something as elaborate as what you have above (although it does look very well thought-out).

This actually looks pretty good to me (`dist` being presumably all generated code), but agree with Josh that starting simple is good. Curious what you’re planning on putting in those `variable` files, though — that looks like the kind of thing that’d typically be handled with stack configuration.