Build documentation like software.
- docs-as-code → entry point & overview
- docs-toolbox → reproducible Docker environment
- architecture-knowledge-toolkit → structured architecture knowledge assets
- profile → Profile of Dieter Baier - as a working example
👉 Start here: https://github.com/docs-as-code-toolkit/docs-as-code
👉 or check, why this organisation exists: https://github.com/orgs/docs-as-code-toolkit/discussions/1#discussion-9830082
Build documentation like software.
Versioned. Reproducible. Automated.
-
docs-as-code 👉 entry point & overview
-
docs-toolbox 👉 reproducible Docker environment
-
architecture-knowledge-toolkit 👉 semantic contracts, metadata, templates, traceability, and AI-assistable architecture workflows
-
profile 👉 Profile of Dieter Baier - Real-world usage: website, CV, and architecture documentation
This toolkit turns documentation into a first-class artifact:
- consistent across environments
- versioned and testable
- easy to maintain and extend
This toolkit is not intended to compete with docToolchain.
docToolchain is a mature Docs-as-Code toolchain for building, converting, publishing, and integrating technical and software architecture documentation. It is especially strong when teams need reliable generation pipelines for formats such as HTML, PDF, DocBook, DOCX, EPUB, static sites, or Confluence publishing.
The architecture-knowledge-toolkit has a different focus. It defines reusable architecture knowledge structures: semantic contracts, metadata conventions, artifact templates, traceability relations, review workflows, and AI-assistable skills for architecture work.
In short:
- docToolchain helps teams publish architecture documentation.
- architecture-knowledge-toolkit helps teams structure, relate, review, and evolve architecture knowledge.
- Both approaches can be combined: this toolkit can provide structured AsciiDoc sources and metadata, while docToolchain or similar tools can render and publish the resulting documentation.
The toolkit deliberately stays publishing-toolchain-friendly. Generated documentation is treated as a derived artifact, while reviewed source documents, metadata, and relations remain the authoritative architecture knowledge base.
We operate one layer above publishing.
👉 Start here: https://github.com/docs-as-code-toolkit/docs-as-code
