Documentation

DocuCommit stores every page as a plain Markdown file in a Git repository you own. There is no database: revision history, diffs, and restore are Git itself, and a git clone is a complete backup of your content.

There are two pieces:

• The desktop editor — Windows, macOS, and Linux. This is where writing happens. Saving writes the file; committing and publishing are explicit actions in the editor — real Git commits, never background sync.
• The read-only server — a Docker container that pulls the repository and serves the docs to everyone else. Readers need no licence and install nothing.

You can run either on its own. A single writer needs only the editor; a team that wants everyone to read the result runs the server as well.

Start here

• Install the editor — download, verify, and open your first repository.
• Repository layout — how pages, sections, and attachments are stored on disk.
• Connect your Git repository — remote, identity, and credentials.
• Publish and get updates — how your edits reach the team, and what happens when they clash.
• Run the server with Docker — publish your docs to the team, with the full configuration reference.

About these docs

The pages you are reading are plain Markdown files in a Git repository, using exactly the layout described in Repository layout — the same format DocuCommit reads and writes.