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

Is there any formal way to annotate stack inputs and outputs with documentation strings to add additional context for their intention and purpose?

Apologies for the delay. I don't know of a formal way to do it, but I'm double-checking with some other folks in case...

Turns out we don't. I've taken the liberty of opening an issue: <https://github.com/pulumi/pulumi/issues/8851>

Fantastic <@U029USY3WB0>; thanks very much!