Skip to content

Add /docs and /articles sections - #1

Merged
Suede-AI merged 1 commit into
mainfrom
docs/site-coverage
Jul 19, 2026
Merged

Add /docs and /articles sections#1
Suede-AI merged 1 commit into
mainfrom
docs/site-coverage

Conversation

@Suede-AI

Copy link
Copy Markdown
Owner

Summary

  • Adds a /docs section: what Suede DNA is, sourcing and verification (honest about the guitargeek-archives → manifest pipeline, what is and isn't verified), search/filter syntax, and an FAQ with FAQPage JSON-LD.
  • Adds an /articles section with five full essays (800-1500 words each) in the site's archival voice: Clapton's 1964-1967 signal chain, a history of the rig diagram as a documentary form, the 1980s-2000s virtuoso rig era, rig archaeology for ear-trained players, and the unphotographed parts of a signal chain (power, cables, mic placement).
  • All facts sourced from the actual repo (README, AGENTS.md, ATTRIBUTION.md, data/*.json, src/lib/search.ts, src/lib/filters.ts) — no invented sourcing process, no fabricated statistics.
  • Wires new routes into header nav, footer, sitemap.ts, and public/llms.txt.
  • Matches existing design tokens and component patterns (PageShell/DocSection mirror the About page's structure; no new hex literals, no new runtime dependencies).

Test plan

  • pnpm typecheck passes
  • pnpm lint passes (no warnings)
  • pnpm test passes (80/80 vitest tests)
  • pnpm build passes, all 11 new routes prerender as static content
  • Local pnpm start smoke test: all new routes return 200, sitemap.xml includes them, header/footer nav renders, FAQPage JSON-LD present, /about unaffected

Adds a documentation section (what Suede DNA is, sourcing and
verification, search syntax, FAQ) and five archive-voice essays on rig
history and tone genealogy. Wires both into header/footer nav,
sitemap.ts, and llms.txt.
@Suede-AI
Suede-AI merged commit 51afcb5 into main Jul 19, 2026
1 check failed
@Suede-AI
Suede-AI deleted the docs/site-coverage branch July 19, 2026 04:06

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aaf9659485

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +10 to +11
{ href: '/docs', label: 'DOCS' },
{ href: '/articles', label: 'ARTICLES' },

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Make the mobile navigation fit narrow viewports

On narrow mobile viewports (for example, 375px), adding these two labels makes the fixed 64px header's minimum content width exceed the viewport: the logo, gap-5, five non-wrapping nav labels, four gap-6 gaps, and horizontal px-6 padding cannot shrink. The header therefore overflows horizontally and its navigation is clipped/off-screen; add a compact mobile treatment, reduce/hide links responsively, or make the navigation scrollable.

Useful? React with 👍 / 👎.

backLabel?: string;
maxWidth?: string;
}) {
return (

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Supply a skip-link target on documentation pages

Every new detail route using this shell renders a <main> with no id="archive", while the root layout's only skip link targets #archive (src/app/layout.tsx:113). On these docs and article pages, keyboard users who activate “SKIP TO ARCHIVE” are left at the same position because the fragment target does not exist; give this main an appropriate target ID or make the global skip-link destination route-aware.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants