How c2pa-org/specifications works
Project type and purpose
• This is a documentation‐site project that uses Asciidoc sources and Antora to generate and publish the C2PA Specifications website. It is not a full‐stack application or service‐oriented microservice architecture, but a static‐site generator pipeline with CI/CD targeting a public spec site (https://c2pa.org/specifications).
File structure
• Top‐level files:
• antora-playbook.yml / antora-playbook-local.yml – Antora configuration that describes how to assemble the site from modules.
• docs/ – Asciidoc modules (ROOT) containing pages, nav.adoc, antora.yml for component metadata.
• buildsite.sh, buildsite-local.sh, makeAntoraPresentation.sh – helper scripts to invoke Antora and local previews.
• .github/workflows/publish.yml – CI workflow that runs on push to build and publish the static site.
• build/site/ – the generated HTML/CSS/JS output.
• package.json – Node.js dependency definitions (e.g. Antora, asciidoctor extensions).
• runLinkChecker.sh, runalex.sh – quality‐check scripts for links and spelling.
README for additional insights
• The README simply states that this repo holds the raw form of the C2PA specs and points to the published site. It confirms the purpose is documentation publication.
Detail without over‐splitting
• Logical step: source management, build orchestration, quality gating, and deployment.
• Avoid extraneous layers like network topology; focus on the documentation pipeline.