Are there already best practices to structure Pulumi code? Do we need multiple “stacks” like in TF land, using “remote state”? Any blog articles that could bootstrap me?

There are plenty of examples here: https://github.com/pulumi/examples and blogs here: https://blog.pulumi.com/ if you want an example of referencing stacks in projects you can visually work with this blog: https://blog.pulumi.com/continuous-delivery-with-gitlab-and-pulumi-on-amazon-eks or refer to the documentation here: https://pulumi.io/reference/organizing-stacks-projects/

I think this is a good link to get started ... https://pulumi.io/reference/organizing-stacks-projects