A writing app for newsletters

1. Draft in the editor. Headings, lists, quotes, code and links, with a word count and a reading-time estimate so you know whether this issue is a three-minute note or a ten-minute essay.
2. Read it once in PDF. A different surface catches what the editor hides.
3. Copy to clipboard and paste into Substack, Ghost or Medium. The formatting survives; images are added in the destination.
4. Keep the Markdown. The same issue can go to a second platform, a static site, or an archive without being retyped.

• Offline. Install it once and the draft works on a train. Newsletter editors generally do not.
• One draft, several destinations. Substack today, Ghost next month, the archive in Markdown. Nothing is trapped in one editor.
• No account for the writing. The publishing account is for publishing; drafting needs no identity.
• No assistant rewriting the opening paragraph. If you want a model involved, take the draft to it deliberately — not by default.
• Privacy. An unpublished issue about a client, a person or a company stays on the device until you choose to publish.

There is no scheduling, no subscriber list, no send button, and no analytics for opens. It is not a newsletter platform; it is the desk the issue is written at. The clipboard export is the hand-off, and it is a clipboard operation rather than an integration — no API key, no account linking, no draft sitting on a server waiting to be published.

The same draft can leave as Markdown for a static site or a CMS that accepts it, or as formatted text for a hosted editor. If the destination is a code repository, Markdown is the format that diffs cleanly; if it is a form with a rich-text box, the clipboard is faster.