For developers and technical writers
- Project docs from a README and a few notes: installation, configuration, usage, FAQ.
- API overviews from a spec or endpoint list — parameter tables and request examples in code blocks.
- Runbooks from incident notes: symptoms, checks, fixes.
- Architecture notes from design docs: components, data flow, decisions.
Markdown in, Markdown out
Code blocks keep their language tags, tables stay tables, and the ZIP export gives one Markdown file per section with working relative links — drop it into a docs/ folder for MkDocs, Docusaurus, VitePress or a GitHub wiki.
docs/
index.md
01-overview.md
02-installation.md
03-configuration.md
...Start from a topic too
No notes yet? Switch to the Topic tab and describe the system — for example “Docs for a Node.js CLI that syncs files to S3: install, config file, commands, errors”. You'll get a sensible skeleton to fill with your specifics.
Frequently asked questions
Does it run or check my code?
No. It organizes and explains what you give it. Check commands and code examples before publishing them.
Can I paste code?
Yes — code, config files and logs are fine. Very large files work best with Pro (100,000 characters).