Public Static Ports Make Site Migrations Reviewable
Wzrrd staging gives joelclaw-style publishing a public review artifact before the canonical domain moves.
Badass.dev is being ported to a public Wzrrd build at badass-dev.wzrrd.sh, which turns a site migration into something you can inspect instead of something you have to trust.
That’s the clever bit: the port isn’t hidden behind a local dev server, a screenshot, or a vague “almost done.” The Wzrrd version renders real pages, real navigation, and real metadata for Badass Courses in a stable public place. You can compare the canonical Badass.dev site against the static port and spot differences before flipping anything important.
The staged build exposes useful structure too: the page advertises wzrrd-render-source="graph-view", includes route metadata, and renders resource IDs like resource:site.page:home. That makes the migration feel less like “copy some HTML” and more like a content graph getting a web projection. That maps cleanly to agent work because agents need inspectable artifacts, not vibes.
For joelclaw, this is a nice pattern: make the intermediate artifact public, linkable, and reviewable. A publishing pipeline that can show its work is much easier to debug, much easier to hand to another agent, and much harder to bullshit.
Key Ideas
- Wzrrd can act as a public staging layer for a site port before the canonical Badass.dev domain changes.
- The badass-dev.wzrrd.sh build keeps real site surfaces visible, including articles, case studies, the Course Builders podcast, the Course Builder, and the sitemap.
- Route metadata and resource IDs make the static port more agent-readable than a plain screenshot or local-only preview.
- The pattern is useful for joelclaw publishing work because every migration step can produce a concrete review artifact.