Publishing handoff
Take the article into your next tool.
Choose a formatted clipboard copy, one article file, or a kit with the files and instructions together. Inspect the result in your own destination before publishing.
Paste into a website editor
- Finish your article in the workspace, compare it with your source, and check the review box.
- Select Copy formatted article. Basic headings, lists, emphasis, code, and supported web links are included. The default copy excludes the title, so you can enter it in your editor's separate title field.
- If your destination needs a document title inside the body, select Include the title when copying formatted text and review again before copying.
- Paste into an editor that accepts HTML clipboard content. The copy also includes a plain-text representation with readable link addresses.
- Check the actual pasted headings, lists, paragraph breaks, title, links, and mobile preview before publishing.
Browser and destination support varies. Some editors discard formatting or change it. This is a clipboard handoff, not a verified CMS integration. If formatted copying is unavailable or blocked, Copy article body supplies Markdown, Download reading page provides HTML, and the visible preview can be selected manually. Your writing stays in the workspace.
Download a publishing kit
Enter a valid title and article, approve the result, and expand Take a complete publishing kit. Inspect the file list and notices, then select Download publishing kit. The ZIP is prepared locally. Extract it into a local folder and open its reading page first.
| File | What to do with it |
|---|---|
| article-body.md | Continue editing or paste into a destination that accepts Markdown. Title and page fields are excluded. |
| reading-page.html | Open locally to read and inspect the article. Manually add it to static hosting only after reviewing its destination name and preview. |
| page-details.json | Use its title, excerpt, description, and suggested safe filename for a manual handoff. Empty fields stay empty. This is not an article import or a universal CMS import file. |
| page.md, when included | Use complete page Markdown in a repository that supports its metadata. The format choice determines whether the file contains a title heading. |
| README.txt | Follow the file-specific next steps and destination review checklist. |
Finish page details when needed
A kit needs only the title and article. Complete the excerpt, description, and a valid filename to include page.md. Otherwise the preview and README list the fields to finish. For page.md, expand Markdown with page details and choose Website supplies the title heading or Include a title heading in the file.
If the filename is empty or invalid, the ZIP filename and page-details slug use a safe suggestion from the title. The original editor field is kept, and the preview explains this decision. The kit does not invent missing summaries, dates, layout settings, or facts.
Choose one destination format
Do not upload the whole kit as a website. For a Markdown repository, add page.md on a feature branch and adapt its metadata to the actual site. For static HTML, choose a destination name for reading-page.html in a directory that serves HTML. For another editor, use the clipboard or article body and enter page fields manually. Review the export guide.
Keep article files and private work separate
The kit and clipboard copies exclude source notes, audience, purpose, article type, private review questions, check results, and sign-in fields. They can still contain private information you put in the article. Review that content before sharing or adding files to a public repository.
A publishing kit is unencrypted and cannot restore a complete workspace. Use an explicit private workspace backup separately to keep source and review notes. Export preferences and temporary kit previews are excluded from those version-1 backups.
Know what the handoff covers
The reading renderer and formatted copy share the same limited Markdown subset. Source HTML, images, relative URLs, and unsupported links remain text. Supported absolute web links load only when a reader follows them. The ZIP uses ordinary stored text files without compression, under a 512 KiB bound. Files carry a fixed archive timestamp, not an edit-history timestamp.
Exporting does not upload, connect to a repository, approve claims, or publish. The draft flag is metadata and works only when your destination honors it. Check the actual saved files, rendering, links, permissions, and factual claims in the destination.