Skip to content

Conversation

@joeduffy
Copy link
Member

@joeduffy joeduffy commented Dec 9, 2025

Still need to

  • Get internal feedback
  • Add an infographic
  • Add a meta image

@claude
Copy link
Contributor

claude bot commented Dec 9, 2025

Documentation Review

I've reviewed the blog post for style, accuracy, and best practices. Overall, this is a well-written and engaging piece that effectively communicates the flywheel concept. Below are the issues found:

Critical Issues

Broken links (line 146):
All three links at the end are broken due to extra slashes:

  • http:///product/neo should be /product/neo
  • http:///case-studies should be /case-studies
  • http:///contact should be /contact
[*Pulumi Neo*](/product/neo) *・ [Case Studies](/case-studies) ・ [Contact](/contact)*

Minor Issues

Typo (line 60):
"example" should be plural to match "These"

These examples share three properties that break traditional infrastructure approaches:

Style Notes

Escaping (line 86, 104, 118):
The escaped "#" characters (\#1, \#2) in the headings appear correctly rendered but are unconventional. Consider whether plain "#1" and "#2" work without escaping, or use alternative formatting like "Foundation 1" or "Foundation One".

Checklist Items from PR Description

Based on the PR description, the following items are still pending:

  • Internal feedback
  • Infographic
  • Meta image (currently using placeholder)

The PR description mentions these are still needed, which is fine for draft review.

Positive Observations

  • Strong opening that effectively hooks readers
  • Clear structure with logical flow from problem to solution
  • Excellent use of specific examples and data points (Jensen Huang projection, ChatGPT query volume, customer examples)
  • Appropriate use of <!--more--> break after opening paragraphs
  • Good balance of technical depth and accessibility
  • Consistent terminology throughout
  • Proper frontmatter with appropriate tags

Fix the broken links before merging. The typo fix is recommended but less critical.

If you'd like me to review updates or help with any revisions, feel free to mention @claude in a comment.

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

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