How to turn a Word document into a documentation site

A Word document is a good way to write forty pages and a bad way to publish them. It usually goes wrong in the same four places, and none of them is a criticism of Word.

• Nobody can search it without downloading it first, so nobody searches it.
• There is no single copy. There is the one in email, the one in Drive, and the one on a laptop, and two of them are out of date.
• You cannot link to a section. Support sends "page 23 of the handbook", which is a page number in a file that has since changed length.
• It reads badly on a phone, which is where a surprising share of internal documentation gets read.

The fix is not to rewrite it. The document is fine; the format is the problem. What you want is the same words at a URL, with search, on a device anyone is holding.

Docszero converts the document at upload and the rule is simple enough to predict before you try it. It hinges entirely on your top-level headings — Heading 1 in Word.

So a handbook with Onboarding, Expenses, Security and Leave as Heading 1s becomes four pages in a folder, each with its own address. A single-topic document with one title stays one page, which is usually what you wanted.

After the import it is ordinary Markdown. Not a locked converted object, not a preview — actual Markdown files you can edit in the browser, reorder by dragging, and export whenever you like.

1. Check your headings first

This is the only preparation worth doing, and it takes two minutes. Open the navigation pane in Word — View → Navigation Pane — and look at the tree. That tree is what you are going to get.

The common problem is a document where headings were made by hand: text bolded and made bigger rather than styled as Heading 1. Word’s navigation pane will show nothing, and the import will produce one long page. If the pane is empty, apply the heading styles before uploading; it is far quicker than splitting pages afterwards.

2. Upload it

Create a project and drop the .docx in. Anything up to 200 MB is accepted, which is more than a document with images in it will ever be. There is no conversion setting to choose and nothing to configure.

3. Read the tree, not the pages

Before you read a word of the content, look at the page list. This is where you find out whether your headings meant what you thought. Pages in the wrong order can be dragged; folders become sections named the way they read.

4. Fix the four usual things

Covered below. None of them takes long, and none of them is caused by anything unusual in your document.

5. Publish

The site builds with search, navigation and a 404 page already in it. On the free plan it lives at your own docszero.com subdomain; on Pro you can point your own domain at it and put a password on it, which for an internal handbook is usually the point.

A conversion is a conversion. These are the parts a machine cannot decide for you, and they are the same every time.

Page titles that were written for paper

A Heading 1 reading "Section 4: Expenses and Reimbursement Policy" was numbered because paper needs numbers. As a page in a navigation tree it wants to be "Expenses". Renaming is fast and it is the single biggest improvement to how the site reads.

Cross-references to page numbers

"See page 23" means nothing on the web. Search the imported pages for "page" and replace each one with a real link to the page it meant. This is the change readers notice most, because it turns a document into something navigable.

Tables that were doing layout

Word documents often use invisible tables to place things side by side. Those come across as real tables, which look odd. If a table has no header row and is not comparing anything, it was layout — make it a list or plain paragraphs.

Screenshots at document scale

Images embedded in Word are frequently scaled for a printed page. They arrive intact and are worth a glance; anything unreadable at page width is worth recapturing while you have the file open.

The usual case is not one handbook. It is a handbook, an onboarding checklist, an expenses policy and two runbooks, all .docx, all in the same folder.

Import them one at a time rather than together. Each document decides its own shape, and importing separately means each one lands as its own folder rather than being merged into a structure nobody chose. Then drag the folders into the order you want; that tree is the navigation the published site uses, so nothing is a surprise.

For a set that large, one thing is worth doing first: decide what the front page says. A pile of imported documents with no index is a filing cabinet. One short page saying what is here and where to start makes it a handbook.