DevlogVersionDocs
Building VersionDocs
Where VersionDocs stands and the early product decisions.
This is the first product update: where VersionDocs stands, and why we are building it this way.
The problem
Technical docs often live in too many places. A spec starts in a wiki, gets reviewed in a Google Doc, then lands in git with three versions of the truth. Markdown is already the right format; collaboration tooling has not caught up.
Decisions so far
A few principles are shaping the build:
- Markdown is the source of truth. No proprietary document format. What you write is what ships, and it exports cleanly to PDF and HTML.
- Review is a first-class workflow. Versioned diffs and structured approvals, not a comment thread bolted onto the side.
- Real-time where it matters. Live cursors and presence for co-writing sessions, without turning the editor into a chat app.
What's next
The repository is public. Next is the editor core and diff view, then the review workflow (request, approve, merge), then early access.
If this fits your team, join the waitlist on the product page.