Files
jinhojang6 5de6f4fbe3 refactor(field-guide): manage UI labels and SEO copy in the content manifest
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
2026-06-30 02:29:00 +09:00
..