Skip to main content
TheDocs
Sign in Book a Demo
Feature

Every revision kept. Every release documented.

Two different problems that get called the same thing: recovering yesterday's wording, and serving the right documentation to someone still on last year's release.

Start free trial Book a demo
  • Unlimited history
  • Side-by-side diffs
  • Reader-facing versions

How does versioning work in TheDocs?

TheDocs keeps two independent things. Revision history records every save of an article with its author and timestamp, lets you compare any two revisions side by side, and restores any of them in one click. Product versioning publishes parallel documentation sets - one per release - that readers switch between, with navigation, search and links all following the selected version.

  • Every save retained; unlimited history from the Growth plan.
  • Side-by-side or inline diff between any two revisions.
  • One-click restore, itself recorded as a new revision.
  • Parallel published versions, e.g. v2 and v3 live together.
  • Fork a version and edit it without touching what is live.
  • Coverage report showing what has not been revisited for the new release.
In detail

Two problems, handled separately

Revision history: undo, with evidence

Someone rewrote a procedure and it was wrong. You need yesterday's text back, and later you may need to prove what it said on a given date.

  • Every save is a revision, with author, timestamp and the change that produced it.
  • Compare any two revisions - not just consecutive ones - side by side or inline.
  • Restore a revision in one click; the restore is itself recorded so the trail stays complete.
  • Filter history by author or date to find the change you are looking for quickly.
  • Revisions are retained for articles that are later unpublished or deleted.

Product versions: serving the right release

Half your customers are on the current release and half are not. Documenting only the newest one quietly fails the rest.

  • Fork the current version to start the next one; edit freely without affecting what readers see.
  • Publish versions in parallel and let readers switch with a selector that persists across pages.
  • Search results, navigation and internal links stay within the reader's selected version.
  • Mark a version deprecated to show a banner pointing to the newer one, without unpublishing it.
  • Set a default version so readers arriving from search land on the current release.

URLs carry the version, so a customer can bookmark or share a link to the documentation for the release they are actually running.

Knowing what still needs doing

The risky part of a new version is not what you changed. It is what you carried forward without checking.

  • Coverage view lists every article inherited unchanged from the previous version.
  • Sort by traffic, so you review the pages readers actually use first.
  • Bulk-assign review to owners straight from the coverage list.
  • Optionally show readers a 'last reviewed for this version' date on each article.

Related features

Review Workflows

Draft, review, approve, publish - with owners, due dates and reminders.

Block & Markdown Editor

WYSIWYG blocks, Markdown and raw HTML in one editor, no mode switching.

Multi-Language Docs

One article, many languages, with translation status tracked per version.

Product Documentation

Ship release notes, guides and reference docs alongside your product.

API Documentation

OpenAPI-driven reference pages that stay in sync with your spec.

Content Analytics

See what readers search for and never find, then fix the gap.
Frequently asked

Questions people ask before they start

Revision history is every save of an article over time - the audit trail. Product versions are parallel published sets of documentation, one per release of your product, that readers can switch between. TheDocs does both, and they are independent.

Thirty days on Starter, and unlimited on Growth and above. Every save is retained, not just published versions.

Yes - side by side or inline, with additions, deletions and moved blocks highlighted. You can diff any two revisions, not only adjacent ones.

Nothing, unless you choose. You can keep older versions published and readable, mark them as deprecated with a banner, or unpublish them. Search and navigation follow whichever version the reader has selected.

Yes. A coverage view lists articles carried forward from the previous version without any edit, so you can triage what genuinely needs revisiting.

Stop documenting only the release you happen to be shipping.

Start free for 14 days. No credit card, no setup fee, and your content is yours to export at any time.

Start free trial Book a 30-minute demo

Questions first? Email sales@thedocs.in or call +91 8585953085.