Skip to content

resources

Everything we know about publishing documentation

Guides for the decisions you make before picking a tool, explainers on how the parts of a docs site actually work, and honest comparisons with the platforms people ask us about. Several of them end by telling you not to buy anything.

Start for freeSee pricing

start here

Decision guides

Questions worth answering before you pick anything, including whether you need a tool like ours at all.

guide6 min

Do you actually need a static site generator?

A static site generator is a good answer to a question a lot of teams have not asked yet. Here is what it actually buys you, what it costs to keep, and the three cases where the honest answer is that you do not need one.

Read
guide6 min

Docs site vs knowledge base vs wiki: which one you need

Three words used for three different things, and picking the wrong one is how teams end up with a wiki nobody trusts or a docs site nobody updates. Sorted by who reads it and who writes it, because that decides everything else.

Read
guide6 min

What documentation should cost in 2026

Published prices for hosted docs run from nothing to $450 a month for what is often the same website. The difference is rarely quality — it is which unit you are billed by, and whether that unit is the one that grows in your company.

Read
guide6 min

How to pick a docs platform you can leave

Everyone checks features before signing up and nobody checks the exit. Six questions to ask before you commit, all answerable in ten minutes on a free trial, and the reason the answers change how much you pay later.

Read

already have the content

Getting your docs in

You already have the content, in a format that is not a website yet. These are the steps, including the parts that will not survive the trip.

how-to6 min

How to turn a Word document into a documentation site

The handbook is a .docx, it is forty pages long, and everyone emails a copy of it. Here is how to make it a searchable website in a few minutes, what converts cleanly, and what you will want to fix afterwards.

Read
how-to6 min

Converting a PDF manual into searchable web docs

A PDF is a picture of a document that has already forgotten how it was built. Converting one is genuinely useful and genuinely lossier than converting a Word file — here is what you get back, and what you will be rewriting.

Read
how-to6 min

Markdown to website, without a static site generator

You have a folder of .md files and you want it on the web. The usual answer is install a generator, pick a theme, write a config and wire up CI. Here is the version where you upload the folder.

Read
how-to6 min

Moving off GitBook without losing your structure

Your pages are Markdown already, so the content is the easy part. The structure lives in a SUMMARY.md and the hints live in GitBook’s own syntax — here is how to get both out with your navigation intact.

Read
how-to6 min

Migrating a mkdocs.yml project in one upload

Zip the repository, upload it, and your mkdocs.yml is read for site name, description, language and navigation. What arrives intact, what a plugin was doing that no config can carry, and how to go back.

Read

under the hood

How it works

One feature at a time: what it does, how it is built, and what it cannot do.

explainer6 min

Why your docs analytics doesn’t need a cookie banner

Cookie banners exist because analytics scripts store an identifier on the reader’s device. Count page views on the server with a hash that changes daily and there is nothing to store, nothing to consent to, and no banner.

Read
explainer6 min

Full-text search in docs without paying for an index

Search on a documentation site does not have to be a subscription. For most doc sets the index is small enough to build at publish time and ship with the pages, which costs nothing and works offline.

Read
explainer6 min

Mermaid diagrams in documentation, with examples

A diagram written as text lives in the same file as the words, reviews like a paragraph and never goes stale in a folder of PNGs. Five diagram types worth using, what each one is for, and when prose is the better answer.

Read
explainer6 min

Contrast and readability in docs themes (WCAG AA in practice)

A brand colour that looks right on a marketing page is often unreadable as a link in body text, and worse again in dark mode. What AA actually requires, which parts of a docs theme break first, and how to stop choosing badly.

Read
explainer6 min

Rollback for documentation, and why version history isn’t it

Version history restores a file. Rollback restores the site your readers are looking at. The difference matters at the exact moment you need it, which is usually ten minutes after a publish went out with something wrong in it.

Read

head to head

Compared with the alternatives

Each one quotes the other product’s own pricing page with the date it was read, and says plainly where that product is the better choice.

vs GitBook

Docszero vs GitBook: what you actually get for free

Both have a free plan. GitBook’s free tier is one user with no custom domain, and the first paid step is $65 per site a month plus $12 per user. Docszero is free for one site and $19.99 a month for ten, domain included.

Readvs Mintlify

Docszero vs Mintlify: free plans, and the cliff after them

Mintlify’s free plan is the most generous of the big docs platforms — five editors and a custom domain. The catch is what comes next: the first paid plan is $450 a month. Docszero Pro is $19.99.

Readvs ReadMe

Docszero vs ReadMe: free tiers, branding and the price of a second project

ReadMe’s free plan gives you one project, one version and a ReadMe badge you cannot remove. Removing it starts at $250 a month. Docszero removes the badge at $19.99 and gives you ten sites.

Readvs MkDocs

Docszero vs MkDocs: the same site, without the pipeline

MkDocs is free and always will be. What costs is the hosting, the CI job and the afternoons. Docszero builds with Zensical, the Material for MkDocs team’s own successor, and publishes it for you.

Readvs Notion

Docszero vs Notion: when a public page stops being a docs site

Notion publishes pages to the web, and for an internal wiki that is often enough. It prices per member rather than per site, charges separately for a domain, and a published page is your live workspace rather than a build you can roll back.

Read