Skip to content

Compostable blog#18804

Open
adamgordonbell wants to merge 11 commits intomasterfrom
agb/compostable-blog
Open

Compostable blog#18804
adamgordonbell wants to merge 11 commits intomasterfrom
agb/compostable-blog

Conversation

@adamgordonbell
Copy link
Copy Markdown
Contributor

@adamgordonbell adamgordonbell commented May 5, 2026

Proposed changes

Unreleased product version (optional)

Related issues (optional)

@claude
Copy link
Copy Markdown
Contributor

claude Bot commented May 5, 2026

Docs review

Strong post overall — confident voice, concrete numbers (five engineers, nineteen clients), good structure with rule + tip-callout pacing, and minimal hedging. Author profile, avatar, meta/feature images, <!--more--> break, and social: block are all in place. The new youtube_id and author_roles template hooks are cleanly implemented and gated correctly so they don't affect existing posts.

A few things to address before flipping draft: false.

Issues

content/blog/seven-rules-ai-first-software-factory/index.md

  • Line 37 — typo (then → than): ...covers rules in more depth then we had time for on stage.

    *Ewan Dawson is CTO of [Compostable AI](https://compostable.ai/), where five engineers run an AI-first software factory: nineteen clients, custom AWS deployments, most of them shipped within a day of contract signing. This article is adapted from his recent Pulumi webinar, and covers rules in more depth than we had time for on stage.*

  • Line 49 — confusing referent: ...whatever this technology was going to become, it wasn't going to become it inside a big enterprise first. The trailing it is a dangling pronoun and reads as a stutter.

    But getting it into the hands of engineers at that company turned into an uphill fight with the Governance, Risk, and Compliance team. Copyright, security, compliance. The concerns were reasonable. They also added up. We were trying to drop a future-of-software-development tool into a process designed for none of that. By the time we'd negotiated a limited trial, I'd already worked out that whatever this technology was going to become, it wasn't going to become that inside a big enterprise first. Startups would. So I left and started one.

  • Line 163 — inconsistent link style: The closing CTA links to https://www.pulumi.com/product/neo/ while the in-body Neo link on line 79 uses the canonical relative path /product/neo/. Per AGENTS.md, internal links should use the canonical relative path.

    *Watch the [original Pulumi webinar](https://www.youtube.com/watch?v=oHNdlWlsR-w). Learn more about [Compostable AI](https://compostable.ai/) and [Pulumi Neo](/product/neo/).*

Stylistic notes (non-blocking)

  • Contrastive heading pattern: Four of seven rule headings use X, not Y / X, don't Y (Switch to using typedoc for TypeScript documentation. #1, Update in the wake of renamepocalypse #2, Set up monitoring and alerting for docs.pulumi.com #6, Do not link @pulumi/cloud in the AWS quickstart #7). It's a recognized AI-writing tic when overused, but here it's a deliberate aphoristic device for a rules listicle, so it works — flagging only because it's right at the threshold. Consider whether one of them could vary phrasing if you want to soften the cadence.
  • Line 72 — Easier to…: STYLE-GUIDE.md flags easy/simple because they judge difficulty. Easier (comparative) is borderline; the doubled Easier to manage… Easier to reframe… reads as a small drumbeat. Soft suggestion to vary one of them, e.g. Cheaper to reframe the problem than to engineer your way through it.
  • Tag infrastructure-as-code: Not in the recommended tag list in BLOGGING.md (which uses feature/scenario tags like cloud-engineering, cloud-native). The other four tags are fine. Consider whether infrastructure-as-code adds discoverability or whether it should drop.
  • Quote on lines 81–83: Since the post itself is a first-person narrative by Ewan (with Adam as as told to), pulling out a quote attributed to — Ewan Dawson inside Ewan's own piece reads slightly oddly. It works as a callout, but you could alternatively style it as an unattributed pull-quote.

Publishing readiness

  • social: block present with twitter, linkedin, bluesky copy
  • meta_image set (meta.png, 232 KB) — verify it uses the current Pulumi logo before publish
  • feature_image set (feature.png, 51 KB)
  • <!--more--> break present after intro
  • Author profile (data/team/team/ewan-dawson.toml) and avatar (static/images/team/ewan-dawson.jpg, 35 KB) both committed
  • All in-body external links present and descriptive (Compostable AI, GitHub Copilot, CDK, AGENTS.md, Pulumi Neo, Pulumi ESC, Pulumi Cloud)
  • Title (53 chars) under 60-char SEO limit
  • Meta description (155 chars) under 160-char limit
  • No animated GIFs as meta_image
  • draft: true — will need to be removed before publish
  • Confirm meta.png uses current Pulumi logos (I can't visually verify in CI)

Template changes

layouts/partials/blog/full-poster.html and layouts/partials/blog/authors.html are scoped narrowly and conditional on the new front-matter fields, so existing posts are unaffected. Both partials are invoked from layouts/blog/single.html (and list.html for authors), and $.context / . resolve correctly for the new field lookups. No regressions expected.

If you'd like another pass after the fixes (or want me to push them as a suggestion commit), mention @claude.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Social Media Review

content/blog/seven-rules-ai-first-software-factory/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

@pulumi-bot
Copy link
Copy Markdown
Collaborator

pulumi-bot commented May 5, 2026 •
edited
Loading

Your site preview for commit 4fd5c05 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-18804-4fd5c053.s3-website.us-west-2.amazonaws.com

@pulumi-bot
Copy link
Copy Markdown
Collaborator

pulumi-bot commented May 5, 2026 •
edited
Loading

Lighthouse Performance Report

Commit: 4fd5c05 | Metric definitions

Page Device Score FCP LCP TBT CLS SI
Homepage Mobile 🟡 67 2.6s 2.6s 858ms 0.018 6.5s
Homepage Desktop 🟢 92 0.6s 0.9s 18ms 0.067 2.5s
Install Pulumi Mobile 🔴 36 4.7s 7.5s 238ms 0.466 7.4s
Install Pulumi Desktop 🟡 77 1.1s 2.7s 20ms 0.011 2.7s
AWS Get Started Mobile 🔴 49 4.4s 7.3s 276ms 0.145 7.0s
AWS Get Started Desktop 🟡 88 1.0s 1.5s 0ms 0.026 2.6s

@adamgordonbell adamgordonbell requested review from cnunciato and dirien May 5, 2026 18:20
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Social Media Review

content/blog/seven-rules-ai-first-software-factory/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

Suggestions (advisory)

These are stylistic notes — they don't block the post.

LinkedIn

  • The last paragraph ("For anyone trying to figure out how to set their team up for what's happening in software now") is a generic closer that could apply to any AI-adjacent post — the pointer already lands in "The blog post is the expanded version"; cut or replace the final sentence with something specific to Ewan's seven rules

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Social Media Review

content/blog/seven-rules-ai-first-software-factory/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

Suggestions (advisory)

These are stylistic notes — they don't block the post.

LinkedIn

  • Final line ("For anyone trying to figure out how to set their team up for what's happening in software now") is a vague closer — name the seven rules or the factory model so the pointer is specific to this article

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

@adamgordonbell @claude
blog: publish seven-rules — flip draft to false
145658c 
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

🟰 Skipping social media review — 1 blog file(s) changed, but social block unchanged. The verdict from the prior run still applies. Comment /social-review to force a fresh review.

@adamgordonbell @claude
ci(social-review): log skip decisions instead of commenting on PRs
7869e89 
The skip-review comment was posting on every push that didn't touch the
social block, drowning active PRs in noise. Switch to a ::notice:: log
line + Step Summary block — same information, discoverable from the
run page, no PR-thread churn. /social-review override path unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Social Media Review

content/blog/seven-rules-ai-first-software-factory/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

Suggestions (advisory)

These are stylistic notes — they don't block the post.

LinkedIn

  • The final paragraph ("For anyone trying to figure out how to set their team up for what's happening in software now") is a generic closer that signals nothing specific — cut it or replace it with a line that names what the article contains without delivering it

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

@adamgordonbell
Copy link
Copy Markdown
Contributor Author

adamgordonbell commented May 5, 2026

@claude where is docs preview link? Can you tell why the various github actions are no longer posting the preview link?

@pulumi-bot
Copy link
Copy Markdown
Collaborator

pulumi-bot commented May 5, 2026 •
edited
Loading

Claude finished @adamgordonbell's task in 1m 59s —— View job

Preview link investigation

  • Check existing preview links in PR comments
  • Investigate the workflow(s) responsible for posting preview links
  • Explain current status and any issues found

Where is the preview link?

It's here, in pulumi-bot's comment from 18:17: http://www-testing-pulumi-docs-origin-pr-18804-4fd5c053.s3-website.us-west-2.amazonaws.com

That URL includes the current HEAD commit (4fd5c05 — merge master into compostable-blog), so the preview is up to date.

Why does it seem to disappear from the thread?

The behavior is by design, but it's easy to miss. In scripts/sync-and-test-bucket.sh (lines 124–144), the preview script:

  1. Searches for an existing pulumi-bot comment containing ``
  2. If one exists → PATCHes it in place (updates the existing comment)
  3. If not → POSTs a new comment

Because subsequent CI runs update the 18:17 comment rather than posting a new one at the bottom of the thread, the preview link stays anchored at its original position. It won't bubble up to the bottom when new commits are pushed — you have to scroll back to find it.

Is anything broken?

No. The GitHub Actions are working correctly — the preview was generated and posted for the latest commit. The UX is just non-obvious: look for the pulumi-bot comment with Your site preview for commit ... is ready! 🎉 near the top of the thread, not the bottom.

If you'd prefer the preview URL to appear at the bottom after each push, the fix would be to remove the "update existing comment" logic and always post a fresh comment, or add the preview URL to a pinned comment. That's a change to scripts/sync-and-test-bucket.sh.

@adamgordonbell adamgordonbell mentioned this pull request May 5, 2026
Merged
4 tasks
@pulumi pulumi deleted a comment from pulumi-bot May 6, 2026
CamSoper
CamSoper reviewed May 6, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@CamSoper CamSoper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@adamgordonbell The pinned preview link is updated. Check the commit in the text. 4fd5c05 is your most recent commit. (@cnunciato added the pinned preview link functionality a few weeks ago)

@adamgordonbell
Copy link
Copy Markdown
Contributor Author

adamgordonbell commented May 6, 2026 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@CamSoper CamSoper CamSoper left review comments

@dirien dirien Awaiting requested review from dirien

@cnunciato cnunciato Awaiting requested review from cnunciato

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@adamgordonbell @pulumi-bot @CamSoper