https://docucommit.se/blog/ Notes on docs as code, Markdown in Git, and self-hosted documentation. en Wed, 26 Aug 2026 00:00:00 GMT https://docucommit.se/blog/make-your-knowledge-base-agent-readable/ https://docucommit.se/blog/make-your-knowledge-base-agent-readable/ Wed, 26 Aug 2026 00:00:00 GMT What agents actually need from a knowledge source — plain text, stable addresses, metadata, a change signal, structure — and how Markdown in Git supplies all five. https://docucommit.se/blog/two-writers-one-markdown-file/ https://docucommit.se/blog/two-writers-one-markdown-file/ Wed, 26 Aug 2026 00:00:00 GMT No CRDTs, no websockets, no locks. How DocuCommit handles concurrent Markdown edits with a content hash on save and a real three-way Git merge underneath. https://docucommit.se/blog/what-actually-leaves-your-network/ https://docucommit.se/blog/what-actually-leaves-your-network/ Wed, 26 Aug 2026 00:00:00 GMT The complete outbound network inventory for DocuCommit: every destination, when it is contacted, what the request contains, and how to opt out. https://docucommit.se/blog/how-we-store-docs-as-markdown-in-git/ https://docucommit.se/blog/how-we-store-docs-as-markdown-in-git/ Fri, 10 Jul 2026 00:00:00 GMT A look under the hood: how DocuCommit keeps every page as a plain Markdown file, versions it with native Git history, and still gives you search, comments, and diagrams — with no database anywhere. https://docucommit.se/blog/why-your-docs-belong-in-git/ https://docucommit.se/blog/why-your-docs-belong-in-git/ Fri, 10 Jul 2026 00:00:00 GMT Documentation tools trap your knowledge in a database you don't control. Here's the case for storing docs as plain Markdown in your own Git repo — and what you get for free when you do.