Everything that ships in the box.

DocuCommit ships a WYSIWYG editing surface over flexmark, the single Markdown engine used everywhere in the product. Type in a familiar toolbar interface; the editor saves a clean .md file with YAML frontmatter. No proprietary blocks, no JSON document trees, just Markdown that diffs cleanly in Git.

Toggle to source view whenever you want to write Markdown by hand. Both views edit the same file.

Most documentation tools either skip diagrams or push you to an external SaaS. DocuCommit ships the whole draw.io editor inside the editor, working entirely offline. A diagram is stored as its .drawio source plus a rendered SVG in the project’s _attachments/ folder, so it versions alongside the prose that references it.

For diagrams you want to track in version control, a fenced mermaid block is the friction-free path. The render pipeline picks it up on both the editor and the server, so writers see the same picture readers do. Because the source is plain text inside the .md, every revision is a clean Git diff, no binary churn, no exported PNG drift.

Reach for the bundled draw.io editor when you need pixel-precise architecture boards; reach for Mermaid when the diagram is part of the prose.

Reference any document from another with an include fence. The render pipeline pulls the live content at read time, so shared definitions, API tables, and boilerplate stay in sync across your library without manual copy-paste.

[[Authentication]] is faster to write than [Authentication](../security/auth.md), and the link survives when the target file gets moved around. The render pipeline looks up the target by uuid, slug, or title at render time on both the editor and the server. Move a document into a different section and every [[wiki]] reference across the library continues to resolve, no global find-and-replace, no stale links to chase.

Fenced code blocks are highlighted with highlight.js on both surfaces. Pick a language tag, write the code, hit save. Readers get the same colours you do. No build step, no extra plugins.

Non-technical writers never touch the command line. DocuCommit runs the Git pull, commit, and push behind friendly Get updates and Publish buttons. If a teammate edited the same lines, a three-pane view shows your version, theirs, and an editable result you build with one click per change, plus a magic wand that auto-merges everything that doesn’t actually clash. And if a document changes or moves on disk while you’re still editing, the editor keeps your text instead of overwriting it silently.

Comments are first-class on the server. Hover any paragraph, leave a comment, @mention a teammate. The thread is stored in a sidecar JSON file on the server, outside the Markdown. The .md itself never gets polluted with discussion markup, and Git history stays clean.

Subscribe to documents, projects, or your own mentions. The server sends SMTP email when relevant events fire, new comments, replies to a thread, edits to a document you follow. Wire it to any SMTP relay; no proprietary notification service required.

A Lucene index built from your repo’s Markdown lets readers and editors find content in milliseconds. The index updates as files change, so newly written content is searchable within seconds in the editor, and on the server as soon as the next sync brings the change in.

Folders model hierarchy; tags model topic. List tags in your frontmatter and the same document surfaces under every relevant tag, without duplicating files or sym-linking sections. The server maintains a tag index alongside the Lucene search index, and the tag pages let you browse the vocabulary already in use.

There is no separate revision table to corrupt or migrate. Every version is just a commit. Both surfaces walk the Git log, render any past revision, and show diffs; the editor can also restore a prior version by writing the old body back to disk for you to snapshot and publish.

Export a single document or an entire project. Markdown gives you the source of truth; self-contained HTML inlines styles and images for one-file sharing; PDF is ready for compliance, archival, or print. No SaaS round-trip.

The split is intentional: the editor is a power tool for writers; the server is a zero-install reader for the rest of the org. Both render from the same .md files, and only the writer’s local Git commits change anything. The server never pushes.

Your content stays on infrastructure you control: the desktop editor reads and writes a Git checkout on your machine, and the read-only server runs as a Docker container on your own infra. The only data that crosses the network is the licensing call (activation ID, hashed hardware fingerprint, OS and app version, and an HMAC-hashed IP) used to keep your seat valid, plus an optional update check against docucommit.se that sends no data and can be turned off. Document content, filenames, and usage telemetry never leave the device.