Skip to content

Rewrite Pulumi vs. CloudFormation page#18908

Merged
jkodroff merged 2 commits into
masterfrom
jkodroff/revise-pulumi-vs-cloudformation
May 12, 2026
Merged

Rewrite Pulumi vs. CloudFormation page#18908
jkodroff merged 2 commits into
masterfrom
jkodroff/revise-pulumi-vs-cloudformation

Conversation

@jkodroff
Copy link
Copy Markdown
Member

Replaces the nested cloud-templates/cloudformation page with a flattened, rewritten comparison at /docs/iac/comparisons/cloudformation/.

Changes

  • New comparisons/cloudformation.md — modernized comparison with a detailed feature table, key-differences sections, and adoption paths
  • Deleted the cloud-templates/ parent and CloudFormation child; all legacy URLs preserved via aliases:
  • New reusable what-is-pulumi shortcode (HTML + markdown pair)
  • Internal link updates in the comparisons index, cloud-template-transpilers/, AWS CDK page, and migrate/
  • Anchor remapping on the AWS CDK page to match the new section IDs

Replaces the nested cloud-templates/cloudformation page with a
flattened, rewritten comparison at /docs/iac/comparisons/cloudformation/.
Preserves all legacy URLs via aliases and updates internal links
accordingly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jkodroff jkodroff force-pushed the jkodroff/revise-pulumi-vs-cloudformation branch from b8e4fbf to 401a2d2 Compare May 12, 2026 17:03
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented May 12, 2026

Docs review

Solid rewrite — the new comparison is tighter, the table is more current, and aliases preserve every legacy path I could find (good SEO hygiene). A few items to consider before merging:

Stale cross-references on the AWS CDK page

Four sections on content/docs/iac/comparisons/cloud-template-transpilers/aws-cdk/_index.md still defer to topical sections in the CloudFormation comparison that no longer exist:

  • Line 64 (### Provider Support), line 69 (### Cloud Native Support), and line 74 (### Dynamic Provider Support) all now point to the same anchor (/docs/iac/comparisons/cloudformation/#cloud-and-service-coverage). Three distinct CDK section headings sending readers to one shared anchor is workable, but it dilutes the "learn more" promise — especially for Dynamic Provider Support, which the new page only mentions in the table cell, not in any prose.
  • Line 83 (### Third-Party CI/CD Support) and line 98 (### Audit Capabilities) link to the page with no anchor. The new CloudFormation page has no CI/CD section and no audit section at all, so readers clicking these "See Pulumi vs. AWS CloudFormation to learn more" links land on a page that doesn't discuss the topic.

Suggest either removing those "See ..." pointers when the destination doesn't actually cover the topic, or inlining a sentence or two on the AWS CDK page so the section still stands on its own. For example, for line 98:

CDK depends on AWS CloudFormation for this capability. CloudFormation provides audit trails through AWS CloudTrail; Pulumi Cloud provides organization-level [Audit Logs](/docs/pulumi-cloud/audit-logs/) that capture user activity, stack updates, secret decryption, policy changes, and more.

Missing table column styling

The deleted cloud-templates/cloudformation/_index.md shipped with an inline <style> block forcing equal-width (33.3%) columns and a slightly smaller font. The new cloudformation.md drops it. Given how long the table cells are (especially the "Modularity and reuse" and "Policy as code" rows), browser auto-layout will likely produce very uneven columns. Worth previewing on a narrow viewport and re-adding the style block — or moving the equivalent CSS to a shared stylesheet — if the rendering looks unbalanced.

Minor

  • content/docs/iac/comparisons/cloudformation.md line 12 (table, "Cloud and service support" row): mentions "first-party native providers for Kubernetes and Azure Native." The same phrasing appears again in the "What is Pulumi?" shortcode and in the prose at line 36. "First-party" is meaningful internally but may read as marketing jargon to a newcomer evaluating the comparison; consider "Pulumi-maintained native providers" or similar.
  • Line 50 of the new file: "Failed Pulumi updates leave the stack in a partially-updated state" — accurate, but the phrasing reads slightly more negative than the CloudFormation row, which leads with "Automatic stack rollback." Worth a small balancing edit if you want the asymmetry not to come through ($"\ldots$ which lets you fix forward without waiting for a service-side rollback," or similar).

The H1 normalization (Pulumi vs. AWS CloudFormation, with the period) and the fixed unbalanced parenthesis on the AWS CDK page (line 50) are nice touches.


Mention me (@claude) if you'd like me to take another look after changes, or to draft the rewrites above.

@jkodroff jkodroff requested a review from CamSoper May 12, 2026 17:05
@pulumi-bot
Copy link
Copy Markdown
Collaborator

pulumi-bot commented May 12, 2026

@pulumi-bot
Copy link
Copy Markdown
Collaborator

pulumi-bot commented May 12, 2026

Lighthouse Performance Report

Commit: 9e3eaea | Metric definitions

Page Device Score FCP LCP TBT CLS SI
Homepage Mobile 🟡 72 2.8s 2.9s 489ms 0.019 6.4s
Homepage Desktop 🟡 82 0.7s 2.3s 32ms 0.028 2.5s
Install Pulumi Mobile 🔴 36 5.0s 7.0s 248ms 0.441 7.2s
Install Pulumi Desktop 🟡 83 1.1s 2.7s 22ms 0.011 1.1s
AWS Get Started Mobile 🟡 54 6.9s 14.3s 245ms 0.003 6.9s
AWS Get Started Desktop 🟡 87 1.1s 1.5s 22ms 0.034 2.5s

Rewrites the opening as a quotable comparison answer, tightens the
meta description, and adds two new sections — "When to choose Pulumi
vs. AWS CloudFormation" and an FAQ covering common doubt-removers
(migration, AWS coverage, pricing, rollback, drift, coexistence) — to
improve discoverability in search and AI answer engines.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jkodroff jkodroff merged commit f27a830 into master May 12, 2026
8 checks passed
@jkodroff jkodroff deleted the jkodroff/revise-pulumi-vs-cloudformation branch May 12, 2026 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants