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)
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