Resource Graph Projections Turn Sites into Portable Artifacts
Resource Graph View plus Wzrrd publishing gives joelclaw a pattern for static, inspectable preview sites with receipts.
Badass.dev running at badass-dev.wzrrd.sh is interesting because the rendered page says the quiet part out loud: it was rendered from a Resource Graph View, with source receipts available for debug only. The public page is just HTML: nav, articles, case studies, podcast links, static pages, and a projection receipt. No app theater required.
The clever bit is that wzrrd.sh is already built for this shape. It publishes static files and directories to wildcard subdomains, supports anonymous 24-hour previews with claim URLs, and exposes agent-readable docs at llms.txt and index.md. That makes a site port feel less like a migration and more like freezing a content graph into a portable artifact.
For joelclaw, the useful pattern is the receipt boundary. The source graph can stay private or debug-only, while the public projection stays small, crawlable, and easy for agents to inspect. That fits static review surfaces and the whole “publish the artifact, keep the pipeline inspectable” vibe.
Key Ideas
- Badass.dev can be represented as a static wzrrd.sh projection, based on the badass-dev.wzrrd.sh page metadata and Joel’s Slack note about porting badass.dev to wzrrd.
- Resource Graph View separates authored source from public render; the public output can expose receipt metadata without dumping private source.
- wzrrd.sh provides agent-friendly publish mechanics: anonymous previews, claim URLs, wildcard subdomains, and machine-readable docs.
- This pattern fits joelclaw review surfaces: build from graph, publish a static preview, keep receipts for debug.