Keep all Field Guide copy in one content source rather than hardcoded strings
plus next-intl keys, per the project's content-single-source direction.
- schema: add `ui` (chrome labels) and `seo` (title/description/chapter
description template) blocks to fieldGuideManifestSchema
- manifest.json carries the actual values
- FieldGuideShell reads chrome labels via a new `ui` prop (no hardcoded
pager text or aria-labels)
- index/[slug] generateMetadata read manifest.seo; remove the now-unused
pages.fieldGuide next-intl keys
- render only http(s) links in a new tab; internal routes use the i18n Link,
while asset/hash/relative/mailto links render as plain anchors
- port the event zone layout image and point the Download link at
/field-guide/img/event-zone-system.png instead of a missing relative path
- de-link "Event Privacy Protocol" (the target 404s on the source site too)
- header logo (lambda + title) is one flex link to logos.co home, vertically
centered — fixes the misaligned lambda
- intra-/field-guide navigation uses Next.js client routing with no fade
cover, so chapter changes are instant
- lift the Paper/Ink theme to the field-guide layout so it persists across
chapter navigation without a flash
Port the reference guide's chrome verbatim so /field-guide is visually
identical to logos-brand-protocol.vercel.app, including dark mode.
- field-guide.css: reference tokens + styles scoped under .fg-shell,
with the Paper/Ink dark theme on .fg-shell[data-theme="dark"]
- FieldGuideShell: reference DOM (lambda header, page reference, theme
toggle, GitHub, print, chapter sidebar, prev/next pager, mobile menu)
- render chapter Markdown into .fg-article via rehype-raw so headerless
tables, <kbd>, and <strong> render faithfully
- hide the global site header/footer on /field-guide so the guide owns
the full viewport (SiteHeaderGate + new SiteFooterGate)
- Public Sans / Fira Code via next/font; Times serif headings
Port the 16-chapter Logos Field Guide from the standalone reference site
into logos.co as content-driven pages, discoverable from the footer and
the global nav.
- content/field-guide/en: manifest (TOC) + chapter Markdown bodies
- @repo/content: fieldGuide schema + loaders, readText fs helper
- /field-guide index + /field-guide/[slug] routes (static export)
- FieldGuideShell (sidebar, pager, keyboard nav) + FieldGuideContent
(react-markdown to design tokens); light theme, site header retained
- Footer "Brand Guidelines" group and nav Explore > Resources links
- sitemap, routes constant, i18n metadata, loader/integrity tests
Closes#65
jinhojang6