-
Notifications
You must be signed in to change notification settings - Fork 256
Description
Some years ago, we released new Pulumi templates (code is in pulumi/templates repo) intended to be more complete examples called "Architecture Templates".
The main content for these templates are in the marketing part of the site: https://www.pulumi.com/templates/
However, most of this content clearly belongs in the docs.
We currently do reference these templates from the docs site (from the cloud pages under IaC), which violates the "links should not go from docs to marketing" style rule.
The templates are organized by architecture (e.g. VMs or container services), which is not optimal - customers are more commonly looking for multiple options in one cloud, not how to implement the same architecture on multiple clouds. Therefore, this content likely belongs under each cloud's section in the docs.
Some open questions:
- Aliases could be tricky here, since we have a single page linking to things for all clouds.
- Do we want a single page for all architecture templates for a given cloud, rather than a separate page for each one (e.g. AWS VMs, AWS K8s Cluster), etc.? (Leaning toward separate pages for better discoverability.)