About MdGenr / the writing desk
01 Why we built this
Writing Markdown should feel like typesetting, not like coding blind. MdGenr exists because the two daily pain points of technical writing never got solved together.
The problem
Technical writers draft Markdown in one tab and check the result somewhere else — a converter site, a repo render, a save-and-refresh loop. Feedback arrives minutes after the typing, and long documents turn into an outline-less wall of hashes.
The solution
A split-pane writing desk: type on the left, see typeset HTML on the right within a quarter second. Headings become a clickable outline, and the two panes scroll together so section 4 of your draft is always next to section 4 of your proof.
How it works
Everything runs in your browser. Markdown parsing, code highlighting, mermaid diagram rendering, and autosave to IndexedDB are all client-side JavaScript. Your draft is never uploaded to a server, because there is no server to upload to.
Who it's for
Technical bloggers shaping a post, open-source maintainers drafting a README, and documentation writers working through a long spec. Anyone whose raw material is plain text and whose deliverable is a formatted document.
02 What we believe
Three rules shaped every feature decision in MdGenr.
Local first
Your draft lives in your browser's IndexedDB and nowhere else. No account, no sync, no Terms of Service standing between you and your own words. Clearing browser data is the only way to remove it — which also means you own the only copy, so export before you switch machines.
Zero ceremony
Open the URL and the editor is already on screen — no signup wall, no onboarding tour, no template gallery to dismiss. The first keystroke starts the document. Writing tools should get out of the way by default.
Long documents first
A five-line README needs no help. A 5,000-line specification needs an outline, scroll sync, and an autosave that will not choke on size. Every feature was tested against the long case, because that is where writing tools break.