# Story: Public site consumes documentation manifest instead of hardcoded copy

Backlog Item ID: SITE-DOCS-MANIFEST

Parent: #340

## User Story

As a documentation maintainer, I want the public site to render content from
versioned documentation or a docs manifest instead of duplicating copy in React
components, so that the site, README, and docs stay aligned with less manual
maintenance.

## Background

The public site currently keeps much of its product copy and section metadata in
`site/src/App.jsx`. That creates duplicate maintenance when docs change. The
site should use documentation as the source of truth where possible, while React
components own layout, interaction, and visual presentation.

## Acceptance Criteria

- Defines a public docs manifest or equivalent content source for site sections.
- Site content for quickstart, command surface, runtime adapters, release
  readiness, architecture, and docs links is derived from versioned docs or
  manifest entries instead of duplicated hardcoded copy.
- `site/src/App.jsx` keeps layout/component logic and no longer owns long-form
  documentation copy.
- Site build fails or reports a clear validation error when the manifest points
  to a missing doc.
- README/docs/site links stay consistent after the migration.
- Public site still builds with `npm run site:build`.
- The implementation avoids runtime network calls; content should be bundled at
  build time or served from local static assets.

## Non-Goals

- Building a full CMS.
- Rendering every internal or backlog doc on the public site.
- Redesigning the whole landing page.

## Suggested Implementation

- Create a manifest such as `docs/site-manifest.json` or
  `site/src/site-content.js` generated from docs.
- Prefer Markdown/frontmatter or a small typed JSON schema for section metadata.
- Add a validation script for manifest paths.
- Keep public/internal classification aligned with #340.

## T-Shirt Size

S

## Suggested Owners

Technical Writer, UX/UI Designer, Developer.