fix(seo): reconcile provider/package count figures across evergreen surfaces - #21065
Open
workprentice[bot] wants to merge 1 commit into
Open
fix(seo): reconcile provider/package count figures across evergreen surfaces#21065workprentice[bot] wants to merge 1 commit into
workprentice[bot] wants to merge 1 commit into
Conversation
…urfaces The registry now lists 310 unique package slugs (verified against https://www.pulumi.com/registry/packages.md), but evergreen marketing and doc surfaces still quoted 150+, 170+, and 180+ (and one page, what-is-pulumi.md, contradicted itself: 180+ in three places, 200+ in a fourth). Standardize on two figures depending on what the sentence claims: - "200+ providers" for provider-specific claims (conservative, true, and already the figure used on the highest-AEO-value pages). - "300+ packages" for claims about the registry's overall breadth, since packages include components (e.g. aws-apigateway, synced-folder) as well as providers. Files touched: content/what-is/what-is-pulumi.md (180+ -> 200+, all 4 occurrences, resolving the page's internal contradiction with its own L47), content/docs/_index.md, layouts/index.llms.txt (L78 only -- L3's 150+ is handled by #20917, not duplicated here), the infrastructure-as-code-tools blog listicle, and the five surviving gads landing pages plus their archetype scaffold. data/header_nav.yaml is site-wide navigation copy ("Browse 170+ cloud providers and packages" -> "Browse 300+ cloud providers and packages") -- flagging this hunk specifically since it renders on every page of the site, in case a reviewer wants to sign off on it separately from the rest. Deliberately left the two dated blog posts (celebrating-20k-stars, pulumi-copilot) untouched: their 160+ figures are point-in-time milestone/announcement numbers, and editing them after the fact would misrepresent what was true when each post was published. --- 🧠 *This PR was created by [workprentice](https://github.com/workprentice).*
github-actions
Bot
added
review:triaging
Contributor
Pre-merge Review — Last updated 2026-08-22T00:35:27ZTip Summary: This PR is a numbers-only sweep across eleven evergreen surfaces (the Review confidence:
Investigation log
🔍 Verification trail34 claims extracted · 27 verified · 2 unverifiable · 1 contradicted · 2 framing-drift · 5 review findings · 1 detector finding
📊 Editorial balanceSection depth, mention distribution, recommendation steering
The two Tier 1 depth outliers are the post's tool-profile catalog and its FAQ — both structural to a survey-style comparison post, both pre-existing, and neither touched by this one-line diff. No balance finding raised against this PR. 🚨 Outstanding in this PRThese must be resolved or refuted before merging.
|
github-actions
Bot
added
review:outstanding-issues
Collaborator
|
Your site preview for commit 26a2921 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-21065-26a2921d.s3-website.us-west-2.amazonaws.com Changed pages: |
Collaborator
Lighthouse Performance ReportCommit: 26a2921 | Metric definitions
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The registry now lists 310 unique package slugs (verified directly against
https://www.pulumi.com/registry/packages.md), but evergreen marketing and doc surfaces still quote 150+, 170+, or 180+, andwhat-is-pulumi.mdeven contradicted itself (180+ in three places, 200+ in a fourth). This PR standardizes on two figures depending on what each sentence claims:what-is-cloud-misconfiguration,what-is-gitops, andwhat-is-pulumi.mditself at L47).aws-apigateway,synced-folder).Files changed
content/what-is/what-is-pulumi.mdcontent/docs/_index.mdlayouts/index.llms.txt(L78 only)content/blog/infrastructure-as-code-tools/index.mdcontent/gads/{backstage,crossplane,infrastructure-as-code,platform-teams,terraform}/index.mdarchetypes/gads.mddata/header_nav.yamlDeliberately left untouched
content/blog/celebrating-20k-stars/index.md("over 160+ packages") andcontent/blog/pulumi-copilot/index.md("160+ cloud providers") are dated announcement/milestone posts. Editing their point-in-time figures after the fact would misrepresent what was true when each was published.layouts/index.llms.txtL3 andlayouts/partials/schema/graph-builder.htmlL185 still say 150+ on this branch (based on currentmaster) — that's not a miss, it's handled by fix(seo): normalize Pulumi language lists on llms.txt, JSON-LD entity descriptions, and /what-is/ pages #20917 (language-list sweep tier 1), which touches the same lines for a different reason. No double-edit needed once both merge.No language-list changes bundled in here — those are #20917/#20919 (in review). This PR is scoped to count figures only.
🧠 This PR was created by workprentice.