Use case 11 · Documentation
One Markdown source of truth for docs scattered everywhere.
Half the product knowledge is in a help centre, a quarter in PDFs on a shared drive, the rest in Word files someone emailed. Bring it all into one place as Markdown, tidy it once, and publish it wherever your team actually looks.
Free account, 10 markdown + 10 AI credits included. No credit card needed.
Today
- Three formats, three search boxes, three versions of the truth.
- PDF manuals nobody can edit or link into.
- Support answering the same question because the doc is unfindable.
With output.md
- Every page and file as Markdown with a consistent heading structure.
- A collection support can ask questions of, grounded in the real docs.
- A ZIP that drops into a docs-as-code repo.
Step by step
How it works, in 5 steps.
-
01
Import the help centre
You do
Point Sitemap mode at your help centre (or paste its URLs in bulk). Review the queue, remove redirects and stubs, process.
You get
Every public help article as a .md file.
-
02
Upload the files
You do
Add PDF manuals, Word specs and Excel reference tables to the same project.
You get
Documents that were locked in PDF are now editable text; spreadsheets become Markdown tables.
TipUpload the newest version of each file only — the project is your clean slate.
-
03
Normalise
You do
Open each file in the editor and align heading levels, remove duplicated intros, fix product names.
You get
A consistent body of documentation for the first time.
-
04
Make it answerable
You do
Collect the files and open Knowledge chat. Ask the questions support hears every day.
You get
A grounded assistant for your team — and a quick way to find gaps in the docs.
-
05
Publish
You do
Export the project as ZIP and commit to your docs repository, or generate a consolidated guide from the collection.
You get
Docs that live where engineers work and update with a pull request.
Why it works
What you get out of it.
Formats stop mattering
Web page, PDF, Word, Excel — everything lands as the same plain Markdown.
Docs-as-code ready
Docusaurus, MkDocs, GitBook, Mintlify and Starlight all read .md files. Export once, import anywhere.
Gaps become visible
When Knowledge chat cannot answer, you have found the article that needs writing.
What it costs
1 markdown credit per page or file.
A 60-article help centre plus a dozen PDFs fits in the Studio pack with room to spare; questions cost 1 AI credit each.
Packs are one-time top-ups — no subscription. See all packs.
Questions
Before you start.
What happens to tables in PDFs and Excel?
Excel sheets become Markdown tables, one section per tab. A PDF comes through as text under an H1 from the filename. Heading styles and table grids are not rebuilt, so dense layouts need a tidy in the editor.
Can multiple people work on the same project?
Projects belong to an account. For team review, export the ZIP into a shared repository — that is where docs-as-code workflows shine.
Does it keep internal links between help articles?
Links are preserved as Markdown links pointing to the original URLs. After migration, a find-and-replace on the domain maps them to the new location.
Try it on your own material.
Paste a link or upload a file, and see the Markdown before you decide anything else.