Feedback home button on subdomains
Every web page served at any <x>.justinsforge.com subdomain that I build (hubs, dashboards, status pages, project landing pages) must include a visible "← JustinsForge.com" button or link that goes back to the root home https://justinsforge.com/.
Why: Justin navigates between many forge surfaces from his phone/desktop. Without a home anchor on every subdomain, he has to retype URLs or clear-and-restart. Adds real friction. Asked for it explicitly on 2026-05-02 while building the hyperframes hub.
How to apply:
- Applies to pages I author (static or generated HTML, dashboards, hubs).
- Does NOT apply to third-party tool UIs we're just exposing through Cloudflare (Hyperframes Studio, Remotion Studio, Frigate, Plex, etc.) — we don't control their chrome and overlaying breaks their UX. Document those as cul-de-sacs and rely on the parent hub to provide navigation.
- Use a top-left or top-right pill: ← JustinsForge.com, sized small, low-attention but always visible. Don't make it the dominant element.
- Sample minimal HTML/CSS:
<a class="forge-home-link" href="https://justinsforge.com/">← JustinsForge.com</a>
<style>
.forge-home-link {
position: fixed; top: 20px; left: 24px;
font: 600 13px/1 'Helvetica Neue', Arial, sans-serif;
letter-spacing: 1px; text-transform: uppercase;
padding: 10px 14px;
background: rgba(0,0,0,0.4); color: #b0bec5;
border: 1px solid rgba(255,255,255,0.1);
border-radius: 999px; text-decoration: none;
z-index: 999; backdrop-filter: blur(8px);
}
.forge-home-link:hover { color: #fff; border-color: rgba(255,255,255,0.3); }
</style>
[Claude Code]