Read this page for the details. It explains what each path does, what each export is for, when the preview refreshes, and which settings matter.
The sample uses a real founder resume, rendered with the same engine used for preview and export.
Create is the default path. Use it when you control the source or want to draft locally in the app.
Audit is for existing files. Upload a PDF or DOCX when the artifact already exists and you want parser-risk feedback first.
The interface stays the same. Resume themes are optional. They change only the document accents, not the workflow.
All four outputs come from the same source and the same render settings, so you are not managing separate versions.
The send-ready attachment. Use it when the application flow expects a final visual document.
The primary portal upload when editable formats are allowed. This is usually the safest submission artifact for ATS parsing.
The plain-text extraction check. Use it to spot broken bullets, missing links, or ugly copy-paste behavior fast.
The machine-readability report. It flags parser-risk, visible-link issues, structure problems, and general submission readiness.
This is the path to use when you have Markdown already or want to draft from scratch in the browser.
Use Upload Markdown if you already have a source file. Use Write in App if you want a local browser draft.
Starter templates are drafting accelerators. Clicking one loads starter content and recommended defaults into the local draft. It does not lock the renderer.
Preview is the inspection step. It renders the current draft with the current page and layout settings so you can review the actual page before export.
Tune Layout covers reset-to-template, resume themes, page size, link display, and the manual font-size and spacing controls. Most users should stay in the quick path until preview shows a real problem.
When the page looks right, export once. The bundle includes PDF, DOCX, TXT, QA, and the original Markdown source.
If the draft or layout settings change after the last preview, the app marks the page as needing refresh. That is intentional. It prevents you from trusting an old page snapshot.
Audit checks a PDF or DOCX resume you already have. It answers one question: is this file good enough to send as is?
The audit checks the same artifact a recruiter or portal would see, not a different source file that never gets submitted.
The audit looks at text recovery, headings, contact details, visible links, and broader structural risks that can make resumes hard to parse.
If the file parses poorly, rebuild it in Create. If it parses well, keep it and apply only the fixes that matter.
The sample is a real founder resume rendered through the same live preview engine and fixed styling used for preview and export. It proves the output on a real document, not a mockup.
The interface stays plain so the workflow is easy to read. The resume can still use conservative color themes for section titles, rules, and links.
The Write in App draft stays in local browser storage on this device. It is there so you can iterate without juggling files while still exporting from one source of truth.
Visible URLs are more reliable for ATS parsing, plain-text extraction, and recruiter copy-paste. Collapsed labels are available for the cleaner visual pass, but they are opt-in.
Start in Create if you have Markdown or want to draft locally. Use Audit only when the resume already exists as a PDF or DOCX and you want to evaluate that artifact first.
It means the draft or settings changed after the last preview. Generate preview again so the page you inspect matches the current state.
Yes. Preview uses the same fixed styling, page size, and layout settings that the export step uses.
PDF is the final visual artifact. DOCX is often the safer upload for portals and ATS parsing. Keeping both gives you the clean visual version and the recruiter-system-friendly version.