Documentation Site — Container
This C3 Component view opens the Documentation Site container and shows how governed content becomes the published AeroSim documentation.
loading...
Components
| Component | Responsibility |
|---|---|
| Docusaurus docs plugins | Organize content sets, routes, sidebars, search, and navigation |
| Local YAML data plugin | Loads governed build-time records for documentation components |
| Draw.io renderer | Renders committed editable mxGraph XML directly in MDX |
| Documentation data components | Render registries, evidence, states, and maps from canonical records |
| Static site build | Produces the searchable site published through Project Pages |
Canonical realization links
Automated engineering validation is allocated to the Documentation Site boundary by the canonical requirement model: AEROSIM-FT-51 ↔ FR-0058 ↔ TASK-0043, TASK-0044, TASK-0045, TASK-0046, TASK-0157, TASK-0162. The human-review page separates application tooling and artifact publication from documentation-governance validation.
Publication flow
Gitea stores and reviews the sources and triggers the documentation build over Git/HTTPS. Docusaurus combines MDX, canonical YAML records, data components, and editable Draw.io sources. The static build is published to Project Pages and served to readers over HTTPS.