Feature 11
Studio blog & door-plate pilot
Building the project in public - starting with a real studio door plate.
Live /studio/ + homepage One use · live showcase scan when configured
About this feature
Why it matters
The site should explain itself the same way the product explains physical objects: short, honest cards. The studio door plate is the first object we dogfood - hours, open/closed, and line updates without reprinting.
Design decisions
Studio blog - card index + posts on the plate, device hub, stack, and framing. Homepage One use · status plate lists concrete scenarios (door scan, run state, special hours, revoke visibility). Try a live scan loads from site/data/showcase-status-plate.json when present.
Safety · privacy · security
Blog posts are static Pages content - no extra tracking. Showcase scan is a normal public resolver object; same limits as any card (no scan analytics by default).
Limits
Blog is manual HTML, not a CMS feed. Only status-plate create template is fully productized; other card types remain research pages.
Future directions
More pilot objects documented as cards, RSS/Atom for posts, organizer-facing build notes tied to artifact-intent launches.