Use the same publication workflow locally and in CI

Install the CLI, keep publication definitions with your project, and build into a dedicated output directory. After editing source content or hints, run the same command again. The generated site is ready for a static host such as GitHub Pages.

Choose a build path

ProjectStart with
A repository of related ontologiesOntology-family builds
A tree of authored documentationWebsite builds
Several independently arranged publicationsPublication targets
Explicit control over collection, planning, and renderingStaged publication commands

Use Getting started for prebuilt installation options and the GitHub Actions guide for CI setup. Pin a released GraphArch version in automation so a rebuild uses the intended generator version.

Rebuild without losing a good publication

Independent sources are collected concurrently. Persistent family builds can reuse unchanged contributions, and bookshelf publications can reuse unchanged book PDFs after checking their inputs and checksums. The Git cache avoids a fresh clone on every remote build.

Generated files belong to their target. GraphArch stages a complete generation before promoting it. Failed or superseded work does not replace the previous complete publication, and files that GraphArch does not own are preserved.

Keep failure policy explicit

The default is to stop on an execution error. --keep-going enables supported diagnostic previews; it does not turn an incomplete release into an approved standard. Quality warnings remain visible in the output and manifest.

Rebuild time depends on source size, queries, and PDF complexity. Large books can take materially longer than an HTML-only reference. Continuous file watching and a live editor extension are not current CLI features; local work uses explicit rebuilds.

Search documentation

Enter words to search this site.