Current State — Reference
Current Nav — What We Have
Four items anchoring to homepage sections only. No links to standalone pages (/gems, /pricing, /agents). A first-time visitor can't see the full site from the nav alone.
Two Structural Proposals
Option A — Full Flat
All key destinations surfaced directly, no dropdowns
Why this works
/gems index, surfacing the 24 AI tools as a standalone pageNav items: Features · Gems · How It Works · Pricing · Blog · [Get Started →]
Gems → links to /gems (full toolkit index)
Pricing → links to #pricing anchor (or /pricing)
Desktop width: ~760px minimum before wrapping
Option B — Grouped Flyout
Key items grouped under product + resources dropdowns
Why this works
Nav items: Product ▾ · Pricing · Resources ▾ · [Get Started →]
Product dropdown: Features / How It Works / Agents / [Gem Categories ×6]
Resources dropdown: Blog / Gems Index
Desktop width: ~460px minimum before wrapping
Information Architecture — Current Site
Option A — What's Exposed
Option B — What's Exposed
Decision Guide — Pick One
| Criterion | Option A — Full Flat | Option B — Grouped Flyout |
|---|---|---|
| Visitor scannability | Everything visible without hovering. Max first-impression clarity. | Pricing always visible; depth behind one hover for product details. |
| Product breadth signal | Adds Gems as a top item — good. Gem categories still require /gems click. | Shows all 6 gem categories inside dropdown — strongest "24 tools" signal at nav level. |
| Mobile experience | Flat drawer, 5 taps, no nesting. Simplest. | Grouped drawer — readable but more scroll. 2-level structure. |
| Engineering effort | Minimal. CSS-only, same pattern as current nav. | Moderate. Needs JS for a11y, keyboard nav, and mobile toggle. |
| Future scalability | 6 items is likely the limit before it breaks visually. | Dropdowns absorb new pages cleanly without touching visible nav structure. |
| Brand fit | Very on-brand — raw, wide, exposed grid. True to the brutalist system. | Clean and professional; feels more conventional SaaS than brutalist. |
| Recommendation | Pick if: you want maximum speed-to-ship and the site structure stays roughly as-is. | Pick if: you want to telegraph the full product depth (24 gems, categories) and plan more pages ahead. |
Engineering Notes — Both Options
- Both options require adding
/gemsas a nav destination — this page exists already at/paperclip/ScopeStack/gems/index.html - Blog nav fix (from SCO-158): both proposals include the full nav on blog pages — this is a separate task for engineering but should use the same nav component produced here.
- Option A can reuse the exact CSS pattern from the current nav with minimal additions. Estimated: <2h implementation.
- Option B needs a
dropdown-openclass toggled on keyboard/touch events, and a focus-trap or escape-key handler for accessibility. Estimated: 4–6h implementation. - Both options should be implemented as a shared nav partial (include or template) so the same markup is used on homepage, blog, /gems, /pricing, and /agents pages.
- "Get Started" CTA can link to
#pricinganchor (current behavior) or/pricingstandalone page — confirm with CEO.