Skip to content

justinsforge.com Home Page Redesign, 2026-06-12

URL: https://mkdocs.justinsforge.com/memory/handoffs/justinsforge-home-redesign-2026-06-12/

You are a Fable 5 worker. Justin wants the justinsforge.com home page redesigned (home page is the priority; other pages secondary). Treat this as a design + build job under Web Builder mode.

Enter Web Builder mode FIRST

Before touching anything, read these (Code Word "Web Builder" spec, CLAUDE.md): - forge/docs/sites-playbook.md (full mode spec, build + deploy flow) - forge/docs/asset-grabber-playbook.md (image sourcing/optimize, the Playwright venv asset grabber, reference_asset_grabber.md)

Critical context, do not get this wrong

  • justinsforge.com is NOT a public marketing website. Justin explicitly wants no front-facing public site on the domain (user_justinsforge_no_public_site.md). The "home page" is his internal hub / landing page: a grid of tiles that link to his <x>.justinsforge.com subdomains (erpnext, requests, browser, mkdocs, etc.). It is the launcher for his own fleet, styled for him, not a sales page. Keep that intent.
  • Conventions that must survive the redesign:
  • Every authored <x>.justinsforge.com page carries a "JustinsForge.com" home pill that links back here (feedback_home_button_on_subdomains.md).
  • Every new subdomain gets a tile on THIS landing page (feedback_new_subdomain_links_home.md). So the tile grid is the source of truth for "what's on my fleet"; the redesign must make adding/maintaining tiles easy.
  • Forge naming + no em dashes in any copy.
  • Default domain for forge surfaces is justinsforge.com; justinkrystal.com is personal/family (project_default_domain_justinsforge.md). Don't mix them.

Find the current site

Locate the existing home page source (likely under forge/sites/<name>/; check for the one serving the apex justinsforge.com, look at the deploy target). Read the current HTML/CSS, screenshot it (/screenshot https://justinsforge.com or via the Playwright path) so you can see what you're redesigning. Inventory the current tiles/links so none are lost.

The redesign

Goal: a sharper, more polished hub landing page. Justin has taste; make it distinctive, not generic-AI-looking (lean on the frontend-design skill's sensibility). Think: - A clean tile/grid of fleet services with icons, grouped logically (infra, media, business, content), each tile linking to its subdomain. - Status-aware feel if cheap to add (online/offline dot per service is a nice-to-have, not required pass 1; note it as an option, don't block on it). - Fast, self-hosted, no heavy framework unless the existing site already uses one. Match the existing stack; don't rewrite the toolchain. - Mobile-first (Justin drives from Venus/Astra iPhone). Must look great on phone. - Dark, modern, on-brand for a homelab command center. Forge identity.

Process (hard gate)

  1. Read playbooks + current site, screenshot it, inventory tiles.
  2. Build the redesign in the site's source dir. Use the asset grabber for any icons/images, optimize them.
  3. Preview, do not deploy. Run /preview-site <name> and surface the localhost + Tailscale URL so Justin can view it on his phone. Do NOT /deploy-site until Justin approves the new look.
  4. Write forge/memory/handoffs/justinsforge-home-redesign-findings-2026-06-12.md (mkdocs URL line at top): before/after screenshots referenced, what changed, the preview URL, and the one command to deploy when he approves. Notify with the path.

Start

Enter Web Builder mode, read the playbooks, find and screenshot the current home page, then design the redesign and stand up a preview. Stop at preview for Justin's approval; never auto-deploy.