Website & Brand System
designhacker.com, the site engine, Token Architecture, and the brand record.
The public face and the design system underneath it. One canon feeds one build.
Domain Law
Only designhacker.com publishes indexable content. Subfolders compound, subdomains never rank. Every other .com is a front door.
dh-site-engine
Notion to build to Cloudflare. The machine that built Bex’s 85-page site in 4 days. One /updates/ stream is feed and blog.
Token Architecture
Layer 1 of the stack. Every color, type, radius, and motion value is a semantic token. Brand-pack swappable, surface-aware.
Brand Record
Magenta #A5205B, dark plum #45123B, coral #EB5E55, blush #EEE4E8. Poppins, exclusive. The brand brief and image prompts.
Blog System
Layer 3. The /updates/ article system. Verdict: the DH engine wins, Strapi stays parked and demand-gated.
Agentic Readiness
Five-Layer Brand Visibility, canon.json, llms.txt, JSON-LD, the machine-legibility layer.
Go deeper
Five-Layer Brand Visibility System
Truth → Proof → Recommendation → Action. The full 5-layer model and the productized 8-step deployment for any brand.
Agentic Readiness
What’s blocked, what’s missing, and the launch baseline every future DH build has to clear.
Site Control Layer
site.json, the SiteConfig schema, and the three-level control panel that drives dh-site-engine. Plus the apex/blog two-engine split.
Brand Record
The full visual identity: palette, tokens, image style, Buddy the mascot, proof, and frameworks.