policy analyze blog post

[Frassle]

Blog post to announce the new policy analyze command added to the CLI (pulumi/pulumi#22250)

[claude]

Docs Review — pulumi policy analyze blog post

Issues

1. Missing meta_image (frontmatter) — meta_image is required for blog posts and is not set. Without it, social shares will use a default placeholder image. Add a meta_image field pointing to a generated or selected image. You can use /blog-meta-image to generate one.

2. Missing bluesky key in social: block (line 14–15) — The social: block has twitter and linkedin but is missing bluesky. These auto-post on merge. Add a bluesky entry (max 300 characters), e.g.:

   social:
       twitter: "..."
       linkedin: "..."
       bluesky: "New in Pulumi CLI: pulumi policy analyze runs policy packs against existing stack state — fast policy testing without running your program or making provider calls."
   

3. Missing documentation — No corresponding docs exist in content/docs/ for pulumi policy analyze. Since this post announces a new CLI command, there should be documentation covering usage, flags, and examples (e.g., under content/docs/iac/cli/commands/ or content/docs/iac/packages-and-automation/crossguard/).

4. First-mention links missing — Per blog review criteria, the first mention of every tool, technology, or product should be hyperlinked:

   • Line 20: "Pulumi CLI" — link to /docs/iac/cli/
   • Line 22: "policy packs" — link to /docs/iac/packages-and-automation/crossguard/
   • Line 30: pulumi preview and pulumi up — link to their respective CLI docs

5. "We just merged" phrasing (line 20) — This will age poorly. Consider more evergreen phrasing like "Pulumi CLI now includes" or "We've added a new Pulumi CLI command."

6. Title contains backticks (line 2) — The title "Introducing `pulumi policy analyze` for existing stacks" renders backticks literally in meta tags and social cards. Consider removing backticks from the title or rephrasing.

Minor suggestions

• Line 26, "Why this command matters" — Consider answer-first phrasing for the H2 per SEO guidelines, e.g., "Faster policy iteration without full deployments."
• Line 71, "In short, this command helps both humans and agents…" — This reads as a summary/TL;DR sentence. Consider cutting it since the preceding list already makes this point.
• The post has no CTA shortcode. Consider adding a {{< blog/cta-button >}} at the end linking to CrossGuard docs or the CLI install page.

What looks good

• <!--more--> break is well-positioned after the intro.
• Social post lengths are within limits (Twitter: 160 chars, LinkedIn: 267 chars).
• Author profile and avatar exist.
• Sentence case on H2+ headings.
• Clean structure, good use of ordered lists.
• No spelling/grammar issues found.
• No AI writing pattern flags (no em-dash overuse, no hedging, varied sentence structure).

Publishing readiness checklist

• <!--more--> break present after intro
• meta_image set and not the default placeholder — MISSING
• meta_image uses current Pulumi logos — N/A (no meta_image)
• Author profile exists with avatar
• All links resolve
• Code examples correct with language specifiers
• No animated GIFs used as meta_image
• Images have alt text; screenshots have 1px gray borders — N/A (no images)
• Title ≤60 chars or allow_long_title: true set
• social: block present with copy for twitter, linkedin, bluesky — Missing bluesky

---

Mention me (@claude) if you'd like additional reviews or help generating the meta image.

[pulumi-bot]

Your site preview for commit 9a68fb6 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-18261-9a68fb6e.s3-website.us-west-2.amazonaws.com.

still need meta images

[pulumi-bot]

Your site preview for commit d572779 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-18261-d5727793.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit aedc70a is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-18261-aedc70ac.s3-website.us-west-2.amazonaws.com.