Repository navigation
Conversation
The status pages feature page had no hero art, no panel and no gallery, a hand-built CSS copy of a status page, and copy that read like a spec sheet. - Demo and status.json now come from @maple/status-page at build time, the same renderer apps/status serves, in sandboxed iframes (operational to outage crossfade). A down monitor is a major outage, as in the product. - Panel and gallery plates rendered from the same snapshot by `bun run screenshots:status-pages` (no stack needed). - Hero engraving from the existing prompt. - Copy rewritten in en/ja/ko: failure threshold, draft incidents, page served apart from the dashboard. Blind A/B with buyer personas and a search quality rater: 4/4 preferred the new copy.
This comment has been minimized.
This comment has been minimized.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 24 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
There was a problem hiding this comment.
🔍 Devin Review: 1 flag
Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
This comment has been minimized.
This comment has been minimized.
Maple review🟢 Confidence 9/10 · safe to merge. The only change since the last review makes the two demo frames inert and adds a screen-reader sentence; contained to static landing markup, no test covers the a11y attributes. Rebuilds the status pages feature demo on
|
The status pages feature page (
/features/status-pages) was the thinnest page in the set: no hero art, no product panel, no gallery, a hand-built CSS imitation of a status page, and copy that read like a spec sheet.What changed
LiveStatusPagerenders@maple/status-page'srenderPageat build time (the same HTMLapps/statusserves) into two sandboxed iframes, operational and outage, and crossfades between them. Scripts are off, styles stay isolated, and the page shows exactly what customers see.StatusPageFeedsprintsrenderStatusJsonoutput for the same snapshot instead of a hand-trimmed copy.deriveComponentStatussays. The old demo showed "Partial outage".bun run screenshots:status-pages(renders locally, no stack needed). The shared snapshot lives insrc/lib/status-page-demo.ts.status-pages-prompt.md.Copy was benchmarked blind (X/Y) with three buyer personas and a search quality rater. Round 1 lost 3 to 1 (too sloganish), round 2 won 4 to 0, and the two lines all four flagged were fixed after.
Screenshots
Notes
@maple/status-pageis now a dependency of@maple/landing(build time only, pages are static).Verification
bun run buildinapps/landing: 315 pages, the status pages route contains both rendered pages.feature-galleries.test.ts40/40 (now also knows the status page captures).🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.