Skip to content

Chart standards: blog posts use chart blocks, not Plotly - #1236

Merged
MaxGhenis merged 3 commits into
mainfrom
max/blog-chart-standards
Sep 30, 2026
Merged

MaxGhenis merged 3 commits into
mainfrom
max/blog-chart-standards

Conversation

@MaxGhenis

Copy link
Copy Markdown
Contributor

The chart standards still told readers that blog posts embed Plotly JSON. Since PolicyEngine/policyengine-app-v2#1231 and #1232, posts draw charts as ```chart blocks that the website renders with Recharts and the ui-kit chart defaults.

This updates docs/engineering/skills/chart-standards.md:

  • The library list and the Plotly exceptions table now mark Plotly JSON in posts as legacy.
  • A new Blog post charts section covers:
    • the three block types (bar, waterfall, stateMap) and where each spec is documented
    • colors chosen by token name
    • the CI test that parses every post's blocks
    • why ui-kit components render unstyled on the website (the tw: Tailwind prefix)
    • screenshotting the live chart for newsletter and social images instead of re-plotting

Docs only; Prettier-formatted.

🤖 Generated with Claude Code

The standards still listed Plotly JSON as the way blog posts embed charts.
Since #1231 and #1232 posts use ```chart blocks rendered with Recharts and
the ui-kit chart defaults. Document the block types, the CI parse check,
the tw: prefix caveat, and screenshotting the live chart for email images.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
policyengine-calculator-next Ready Ready Preview Sep 30, 2026 1:05am UTC
policyengine-website Ready Ready Preview Sep 30, 2026 1:05am UTC

Request Review

…types (review)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MaxGhenis

Copy link
Copy Markdown
Contributor Author

Admin-merged at head 5f64da7 after: gh pr checks exit 0 (12/12 pass), MERGEABLE, not draft, no CHANGES_REQUESTED. An independent Opus 5.5 reviewer approved in round 2; every mechanism claim was checked against origin/main (chart types, color names, CI parse test, tw: prefix, legacy formatter). The only block is the required approving review, which the author cannot give on their own PR. Docs only.

@MaxGhenis
MaxGhenis merged commit 0e0f9e3 into main Sep 30, 2026
12 checks passed

This branch was successfully deployed

2 active deployments
Preview – policyengine-website — 5f64da71 Deployed Sep 30, 2026 by vercel[bot]
Preview – policyengine-calculator-next — 5f64da71 Deployed Sep 30, 2026 by vercel[bot]
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.

1 participant