Publish documentation from the knowledge you maintain
GraphArch turns authored explanations and structured RDF sources into connected websites and review documents. Maintain the content once, then choose how each audience should read it: a specification, a companion website, a PDF, or a library of module books.
What GraphArch does
| Feature | What it gives your project |
|---|---|
| Collect existing sources | Read Markdown, RDF files, repository content, and selected results from SPARQL endpoints. |
| Reusable content and hints | Connect explanations to stable subjects and arrange them differently for each publication. |
| Queryable documentation graph | Inspect the content, relationships, provenance, and exact revision behind a publication. |
| Websites and PDFs | Publish final static HTML and typeset documents from the same collected knowledge. |
| OWL class diagrams | Navigate class neighborhoods with UML notation, authored labels, and scoped constraints. |
| Quality review | Show competing annotations and missing descriptions to reviewers without discarding source statements. |
| Local builds and CI | Use the same CLI locally and in automation, with explicit failures and ownership of generated files. |
| Extend GraphArch | Add focused adapters and publication styles without making every source or output follow one format. |
Choose what to document
The Documentable Things catalogue describes how GraphArch recognises authored content, ontologies, ontology families, constraints, taxonomies, and use-case trees. Source location and documentable subject are separate choices: an ontology can live in a file, a repository, or a SPARQL endpoint.
See the result before configuring it
Browse the showcase gallery for generated publications, then follow Getting started to install the CLI and choose a publication guide. These pages describe implemented capabilities; new source types and richer specialist interfaces require further development.