Semantic HTML
Headings, lists, tables and code come out as the tags they are, with no classes, wrappers or inline styles. The stylesheet you already have does the rest.
Pikkola MD, tool No. 25
The source on the left, the document on the right, rendered as you type. Then take it out in the shape the place you are sending it to can read: semantic HTML, rich text, Slack marks, a table of contents, or an A4 page.
The editor
Type on the left. The right pane is the document, updated on every keystroke, tables, task lists and highlighted code included. The buttons above it decide what leaves the tab.
Nothing is saved or sent. Closing the tab discards the document. ⌘S or Ctrl+S saves a .md file
What leaves the editor
A preview is half of an editor. The other half is what you can carry out of it, and each destination asks for a different shape.
Headings, lists, tables and code come out as the tags they are, with no classes, wrappers or inline styles. The stylesheet you already have does the rest.
One press puts the formatted document on the clipboard, so it lands in Docs, Word or a mail window with headings and tables intact.
Bold, links, quotes and checklists rewritten into the marks Slack understands, with a table set in a code block so the columns stay straight.
Every heading collected in order, nested by level and linked to its place. Copy it as a Markdown list or an HTML nav.
Words, characters with and without spaces, headings and reading time, counted from the rendered text as you type.
The print dialog opens on the document alone: A4 margins, black text, code that wraps, and rows that keep their page.
Why this one
No preview tab and no round trip. The right pane is the document as a reader would see it, including tables, task lists and highlighted code.
Most editors stop at the preview. This one starts from the question of where the text is going, and gives each destination its own button.
No upload, no account, no draft on a server. The page's security policy blocks every other origin, so the document cannot go anywhere you did not send it.
The document lives in the textarea and in memory. Reloading the page starts a fresh one, and closing the tab throws it away, which is the point when the notes are not yours alone.
Read the privacy noteQuestions
No. Parsing and export run as functions in the page, and the content security policy blocks every other origin. Nothing is written to storage either, so a reload starts a fresh document.
GitHub flavored Markdown: headings, bold and italic, strikethrough, links and images, inline and fenced code with highlighting, blockquotes, nested lists, task lists, tables with alignment, and horizontal rules. HTML typed into the source is shown as text, never run.
The rendered document as semantic tags: h1 to h6, p, ul, ol, table, blockquote, pre and code. Classes, wrappers, inline styles and event handlers are removed. Heading ids stay, so a table of contents pasted with the document keeps working.
Print, or Command and P, opens the browser dialog with everything but the document hidden. The page is set to A4 with 18 mm margins, code blocks wrap instead of running off the sheet, and table rows are kept on one page. Choose Save as PDF to keep a copy.
Slack's own formatting. A heading becomes bold text, a link becomes <url|label>, a task list becomes boxes, and a table becomes a code block, because Slack has no table. The converted text is copied so you can paste it into a message.
Yes. Download writes a .md file with your text unchanged, and Print can save a PDF. The editor keeps no copy of its own, so the file is the copy.
The two panes stack, the editor above the preview, and the toolbar scrolls sideways. A long document is easier on a desktop, but a note and a PDF work anywhere.
Paste as plain text to keep the Markdown clean. A rich paste arrives with its own formatting, which the editor treats as text and the preview shows as written.