Export documents

All Writer supports these common export paths:

• Markdown ZIP: keeps .md files, folder layout, and the @system rules folder.
• AI share cards: turns selected chapters into shareable card assets.
• Web package: exports a ZIP with index.html and standalone CSS for browser preview or static handoff.

The codebase still contains the Word AI dialog and backend word-export workflow, but the main Export dialog currently hides that entry. Use Word generation only when it is visible in the product; otherwise export Markdown ZIP or Web package first and finish .docx externally.

How to export

1. Use File → Export, Ctrl+E where available, or the toolbar Export button.
2. Choose Markdown ZIP, AI share cards, or Web package.
3. Choose a save path (desktop) or download (web). For AI share cards, configure the required scope and options in the dialog.
4. Wait for the export to finish.

ZIP layout (example)

project-name.zip
├── @system/
│   ├── style.md
│   └── characters.md
├── chapter-01/
│   └── section.md
└── README.md

Use the ZIP for backup, Git, migration, or editing in other Markdown tools.

Web package

Use Web package when you want a reviewable static page:

• The ZIP contains index.html and CSS.
• It can be opened directly in a browser.
• It works well for review, preview, archival, and static handoff.

Word handoff

The main Export dialog does not currently present Word as a regular option. If a Word generation entry is visible in the product, follow that dialog. If not, export Markdown ZIP or Web package first, then create .docx with Word, WPS, LibreOffice, Pandoc, or another local workflow.

Convert to PDF / HTML

Use Pandoc (or similar) on extracted Markdown files:

pandoc chapter.md -o chapter.pdf
pandoc chapter.md -o chapter.html

All Writer does not provide built-in PDF export. Use exported Markdown or Web package output with Pandoc, browser print, Word, WPS, LibreOffice, or another external workflow.

Tips

• Large projects: export after major milestones.
• Check chapter order, headings, and @system before generating handoff files.
• For local-only desktop projects, use Markdown ZIP or Web package first.
• Pair with Outline editing to keep structure clean before export.