Skip to content

Teach the review machinery that HCL is a first-class Pulumi language - #22992

Draft
CamSoper wants to merge 2 commits into
masterfrom
claude/project-thread-ertmu7
Draft

CamSoper wants to merge 2 commits into
masterfrom
claude/project-thread-ertmu7

Conversation

@CamSoper

@CamSoper CamSoper commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Requested by Cam · project thread

Proposed changes

Marketing wants HCL treated as a first-class Pulumi language, in the same tier as Python and TypeScript, and wants the docs pipeline to find and fix the places where it isn't. The August 2026 release already says it ("write programs in HCL as a first-class Pulumi language"), but none of the review machinery knew. This PR teaches it, so reviews flag the gaps and the glow-up lane executes them.

  • AGENTS.md: new HCL as a Pulumi language section, modeled on "AI and agent positioning". It covers naming (HCL vs. Pulumi HCL vs. Terraform HCL), using {{< pulumi-languages >}} for language lists, hcl chooser tabs where Pulumi HCL supports the feature (never invented), dropping the "HCL is the enemy" and second-tier framing ("config languages like YAML and HCL", "a general-purpose language is the recommended destination", "real languages, not DSLs" next to a list that includes HCL), keeping staying in HCL as a migration path, neutral comparison pages, no ranking language, and {{% hcl-note %}} for older blog posts instead of rewriting them.
  • docs-review criteria: shared-criteria.md gets an HCL criterion that applies to every review. HCL findings are ⚠️ (editorial), so the content-review fix lane banks them and the glow-up lane executes them. docs.md adds HCL gaps to its pre-existing-issue scope, and blog.md adds the hcl-note check.
  • glow-up.md: HCL checks in the text analysis and the content-enhancement taxonomy, which the unattended glow-up lane's secondary sweep applies.
  • review-existing-content: HCL gaps are listed among the findings the fix lane reports and banks, without applying them.
  • Blog known-issues index: new hcl-positioning category in the taxonomy, validate-findings.py, and the findings schema.
  • hcl-note shortcode: drops "alongside general-purpose languages like…", which kept the two-tier framing, for "alongside TypeScript, Python, Go, C#, and Pulumi's other languages".
  • data/blog_tags.yaml: moves hcl from the non-Pulumi ecosystem group to languages.

What this doesn't change: the fix lane still applies only high-confidence fixes, and glow-up's bounds (no superlatives, 400 lines, protected frontmatter) are untouched. The sitewide language order in pulumi-languages (HCL last) is left for a messaging decision.

make test-review-pipeline and make lint pass.

Related issues (optional)

Brand guide counterpart: pulumi/marketing-web#387.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RR4MzpSTovKZAqW9HVfd74

Add an AGENTS.md section on HCL positioning and point the docs-review
criteria, glow-up taxonomy, content-review lane, and blog known-issues
taxonomy (new hcl-positioning category) at it, so reviews flag HCL gaps
and the glow-up lane executes them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RR4MzpSTovKZAqW9HVfd74
Name the second-tier phrasings the audit panel found, drop the
two-tier wording from hcl-note, and file the hcl blog tag under
languages instead of non-Pulumi tools.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RR4MzpSTovKZAqW9HVfd74
@pulumi-bot

Copy link
Copy Markdown
Collaborator

@pulumi-bot

Copy link
Copy Markdown
Collaborator

Lighthouse Performance Report

Commit: 2271fd6 | Metric definitions

Page Device Score FCP LCP TBT CLS SI
Homepage Mobile Error - - - - -
Homepage Desktop Error - - - - -
Install Pulumi Mobile Error - - - - -
Install Pulumi Desktop Error - - - - -
Resources concept Mobile Error - - - - -
Resources concept Desktop Error - - - - -

This branch was previously deployed

1 inactive deployment
testing — 2271fd6e Deployed Nov 17, 2026 by CamSoper via Install deps and build site #18559
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