# Subnautica2Maps — Inner Page Design Refresh Content-Fit Matrix

Task: t_13066796
Date: 2026-05-21
Source priority: current repo routes + QA/Owner Review + SEO/GEO recheck + PRD/copy pack
Design tone: Retro-futurist deep-sea HUD; dark tactical console, scanner lines, coordinate grid, phosphor cyan + kelp green + pressure amber. Not SaaS.
Fonts: Space Grotesk display + IBM Plex Sans body. No Inter/Roboto/Arial.
Compliance red lines: fan-made/no affiliation visible but subordinate; no official logos, key art, screenshots, copied tiles, copied competitor marker UX, copied long-form text, official/complete/100% accurate claims.
Product value guardrail: every screen must still feel like a usable map/resource/player-task product, not a safe placeholder wall.

## Route scope from current repo/sitemap

Indexable current routes:
- `/map/`
- `/resources/silver/`
- `/resources/copper/`
- `/guides/how-to-find-coordinates/`
- `/guides/does-subnautica-2-have-a-map/`
- `/legal/`
- `/privacy-policy/`
- `/terms-of-service/`

No current committed routes for `/biomes/[slug]`, `/blueprints/[slug]`, `/resources` hub, `/blueprints` hub, or `/locations/[slug]`. These remain design follow-up templates only; do not put them in sitemap/design-go until route + copy + data exist.

## QA / review constraints reflected

- Parent QA t_abe63d4f: QA_GO. Residual P2: 390px bottom sheet information density high; 1440px marker density visually dense.
- Owner review t_5dba8672: approved moving forward; public external publish still needs confirmation.
- SEO recheck old blockers are mostly remediated in current repo: sitemap no longer lists biome URLs, current route files include canonical/schema helpers, `/map` has H1. Design must preserve these fixes.

## Page matrix

| Page/template | H1/H2/H3 + copy source | SEO/content load | Above fold placement | Folded/downstream placement | Required visual container | Visual risk | Design decision |
|---|---|---:|---|---|---|---|---|
| `/map/` interactive map | Current repo `src/app/map/page.tsx`; PRD §8 map states; copy pack §2 | High, tool-first + FAQ | H1, short answer, search/filter toolbar, marker count, map surface, selected marker sheet, route helper access | Data transparency, confidence legend, FAQ, legal note | Split tactical console: left search/layers, center self-made bathymetric grid, right/bottom marker drawer; mobile bottom sheet | Dense markers, 390px bottom sheet overload | Make filters collapsible on mobile; use progressive disclosure for route/confidence/source; preserve 44px chips; avoid putting long FAQ before tool |
| Resource detail template `/resources/{slug}` covering `/silver`, `/copper`, noindex `/sulfur` | Current repo resource route; copy pack §5; marker JSON | High for silver/copper; sulfur limited/noindex | H1 pattern, short answer, CTA to filtered map, marker count/confidence/index cards, best marker | Coordinate table, source/provenance, lazy YouTube/source support cards, FAQ | Resource dossier card + mini map strip + coordinate table; source confidence badges | Long coordinates/source text can become a wall | Keep top answer compact; put source line in table row; videos as click-to-load cards after map action; sulfur clearly limited/noindex |
| `/guides/how-to-find-coordinates/` | Current repo guide; copy pack §2 route helper + §9 guide structure | Medium-high, answer + steps | H1, answer, 3-step coordinate interpretation, CTA to route helper | Source confidence, coordinate examples, FAQ | Tutorial scanner panel with X/Y/Z readout and route clue mock | Too abstract if no map context | Include mini route calculator visual, depth delta/bearing readout, and map CTA; avoid generic article layout |
| `/guides/does-subnautica-2-have-a-map/` | Current repo guide; copy pack §8/FAQ | Medium, answer-first | Direct answer, fan-made map CTA, utility value | Why players use coordinates, what this map can/cannot claim, FAQ | Answer card + compare strip: in-game navigation clues → fan-made map utility | Could look like thin SEO article | Add useful task cards and internal map/resource links; no official claims |
| `/legal/` | Current repo legal page; PRD §10 | Medium-low but compliance critical | Fan-made disclaimer, source attribution, media policy, DMCA contact | Trademark statement, correction/removal process | Legal command center: four clear cards, quiet hierarchy | Disclaimer can dominate product | Keep readable but subordinate; no scary wall; email visible |
| `/privacy-policy/` | Current repo privacy page; PRD privacy guardrails | Medium-low | No account/no raw coordinates promise, localStorage progress, analytics summary | YouTube embeds, contact data, user rights | Privacy controls panel with local-only route calculation diagram | Could duplicate legal/terms | Unique privacy-specific hierarchy: local storage, analytics, embeds |
| `/terms-of-service/` | Current repo terms page; PRD legal boundary | Medium-low | Fan-made tool, no warranty, Early Access accuracy | Acceptable use, source corrections, trademark disclaimer | Terms cards with risk labels and player-safe framing | Could duplicate legal/privacy | Unique terms-specific hierarchy: use conditions, no warranty, acceptable use |

## Design system contract

Tokens:
- Background: `#041012`
- Surface: `#071A1D`
- Surface elevated: `#0B262A`
- Text primary: `#E7FFF8`
- Text secondary: `#8CB7B0`
- Primary accent: `#27E7C5`
- Secondary accent: `#B8FF5C`
- Warning/accent: `#FFD166`
- Error/spoiler: `#FF5C7A`
- Grid line: `rgba(39,231,197,.14)`
- Border: `rgba(136,255,226,.18)`

Layout rules:
- No centered SaaS hero.
- No symmetric 3-column feature grid as main structure.
- No emoji icons; use Material Symbols or custom SVG strokes.
- Mix square HUD panels with one rounded active marker drawer; radius should not be uniform.
- Mobile: single-column or stacked tool panels, 44px controls, no horizontal overflow at 390/430px.

## Follow-up templates not currently in repo

- Biome detail: design only after committed route/data exists; use biome overview + resources + hazards + source/version notes.
- Blueprint detail: design only after committed route/data exists; use scan count + coordinates + required materials + related POI.
- Location/POI detail: design only after committed route/data exists; use coordinates + depth + route + nearby resources.

Design status for current route scope: proceed to official Stitch generation.