The store · stack
Content-as-Code Registries
4 systemsOne source of truth; many surfaces follow.
The registry pattern, four ways: a single content-as-code list drives many surfaces at once. Add-ons power the marketplace and /tools, the utilities registry mints 60+ tool pages, the command registry routes every action, and the email identity registry guards every From line.
Add-ons Registry
One catalog that powers the marketplace and the public tools page.
A content-as-code registry of installable add-ons (analytics, social, productivity boards). The same source renders both the /profile/settings marketplace and the public /tools landing, so the two can never drift.
Utilities Registry
Sixty-plus client-side browser tools, each its own SEO page.
A registry of free, client-side browser utilities (converters, encoders, generators, formatters). Each tool is statically generated with its own metadata, FAQ and WebApplication JSON-LD. Nothing leaves your machine.
Command Registry
One declarative list of every destination and action on the site.
A single source of truth for the site’s stable destinations and actions, role-gated and grouped. The nav, footer sitemap, omnibar and concierge all read it — so they never re-derive their own lists.
Email Identity Registry
Per-surface "From" lines so no brand leaks onto another.
Every transactional email and magic link sends through one path with a pure, unit-tested per-surface identity registry. Only the address and domain come from EMAIL_FROM; the display name (and, for court mail, the local-part) come from the identity — so one surface’s brand can never leak onto another’s mail.