Markdown in, typeset PDF out — with a round trip
If you would rather your resume were a text file in a repository than a document in a cloud editor, this is the workflow: plain-text source, real typesetting on export, and a lossless path back from the exported file to the source.
The round trip
Export Markdown and you get a clean, readable document — headings, bullets, ordinary prose — with the full structured payload tucked into a trailing HTML comment. Commit that file. Edit it by hand if you like. Drag it back in and the editor restores exactly what you had, theme and all.
JSON export is the same idea without the prose layer: the resume object, formatted, diffable, and a stable interchange format.
Why version-control a resume
- You keep every version you actually sent. When a recruiter references a bullet from March, you can read the file from March.
- Diffs are readable. Rewriting a summary shows up as a two-line change, not a mystery.
- Branch per application. Retarget a resume for a specific posting without losing the general one.
- No proprietary lock-in. The source is text. It will still open in thirty years.
Fits the rest of the toolchain
The Markdown export drops straight into a static site, a GitHub profile README, or a plain-text application form. The JSON export is a plain object you can script against — filter roles, generate a tailored variant, feed it into your own template — and bring back in through the same import path.
For a technical audience, the Terminal theme sets the whole document in JetBrains Mono; Modern and Meridian are the safer picks when the file is going through a portal first.
No build step, no dependencies
The usual resume-as-code setup is a LaTeX distribution, a template repo, and a build pipeline you re-learn every time you touch it. This is a web page: paste the Markdown in, pick a theme, download the PDF. The typesetting is already done, and the source stays text.
Frequently asked questions
Can I write my resume in Markdown and export a PDF?
Yes. Import a Markdown file, pick a theme, and export a typeset PDF or DOCX. The Markdown stays your source of truth.
Does the Markdown export round-trip back into the editor?
Yes, losslessly. The full structured data is appended as an HTML comment, so re-importing restores your exact content, theme, font and spacing.
Is there a JSON export I can script against?
Yes. JSON export gives you the resume object as formatted, diffable text, and importing that JSON restores the document exactly.
Do I need LaTeX or a build pipeline?
No. There is no toolchain to install — the typesetting and PDF generation happen in the browser page itself.