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

screencapture-pulumi-docs-reference-pkg-aws-sqs-queue-2020-03-31-16_04_44.png

Here's a birds-eye view of the new content layout.

This approach is fantastic. Is there anyway to consume the documentation template as a library author for my `ComponentResource`s?

<@UH9NBAJ68> not yet - but we will be adding that! This documentation is all driven off of a new canonical language-agnostic schematization of the Pulumi resource model. That schema doesn’t yet represent component resources, but we’ve designed it with the intention to extend to components in the near future.

That’d be amazing. I’m currently using mkdoc + typedoc for kloudlib but i’d love to use something that feels more _pulumi native_ so that users can get a consistent documentation experience.

The new doc is very clear ! Great improvement :+1:

I’ll add below some feedbacks

image.png

I think also that right menu could be improved.

Current menu :

resources, datasources and types are mixed

I’d prefer (my opinion) something like:
```- Virtual Machine resource
    - Arguments
    - Outputs
- Data sources
   - Lookup…
   - …
- Supporting types```

<https://www.pulumi.com/docs/reference/pkg/> still has the issue of calling everything a cloud provider.

<@UGDSK5RNC> out of curiosity - what name would you prefer to see used here? 

Just like TF, everything is a provider, then you have major cloud, cloud, infrastructure software, network, vcs, database, etc.

<https://www.terraform.io/docs/providers/index.html>

<@UPA9DFVUH> thanks for the notes. On the “navigation” point - is that about wanting anchors on the headers so you can deep link to them?  On the nav structure - we could definitely add some more structure there. Note though that the “Loookup” section is not about “data sources”  (in the Terraform sense) but about resource getters. The “data sources” are on separate pages listed under “functions”. 

<@UGDSK5RNC> understood - we will be significantly restructuring that main reference docs landing page as we roll out the remaining new reference docs pages and will be looking to add some more substructure around the list of all providers. Thanks. 

Hi <@UB3BGTV63>, I don’t think that we currently can select a specific version of the provider doc. For example, there lot of changes between azure provier 1 and 2, and people on version 1 will not understand why the doc is not sync with their version.

<@UPA9DFVUH> Yes - that is right - we currently just have a single version synced with the latest released version.  We would definitely like to be able to show other versions as well - especially when there are significant major-version bumps like with Azure.  This is something we'll be adding after the initial wave of work on these new docs.