A markdown-based word processor that produces polished, branded PDFs.
LX Draft is a WYSIWYG word processor built on markdown. You write and format your document on a clean, continuous editing canvas, and the artifact you ship is a polished, branded PDF. Think of it as "Word, but markdown-based, and tuned to produce beautiful print-ready documents."
Because the underlying content is markdown, LX Draft is designed to work well with AI agents. An agent can author a precise, well-structured document — a specification, a proposal, a report — in markdown, and a human can then refine it in the editor. Throughout, the PDF is the deliverable: the thing you send to a client, attach to a project, or file as a record.
Because LX Draft documents are markdown under the hood, they are often authored by an
AI agent. You hand the agent a short writing guide, describe the document you need, and the
agent produces a structured .lxdoc (or markdown) file you import here. The guide covers the
frontmatter schema, LX-specific extensions (callouts, CSV tables, equations, fields, signatures), how to
deliver embedded images as a bundle, and the validation rules your output must pass.
This is the most important concept to understand. LX Draft runs in two modes, and a document always knows which mode it belongs to.
You open LX Draft directly in your browser and work on a document on your own. Documents are plain
.lxdoc files that you open and save on your own computer. There is no project
governance: you decide when the document is finished, and you self-sign it on an
honour-system basis. This is the "Word, but markdown-based, producing beautiful PDFs" experience.
LX Draft can also be launched from Lexis, the project-management suite. In this mode the document is a controlled project artifact. Its lifecycle — releases, version history, and signing — is owned by Lexis, and the document's content lives in the project's Google Drive folder rather than on your computer.
Use Save to computer (or press Ctrl+S) to write the
.lxdoc file.
LX Draft keeps a Recent files list so you can jump back into recent work. Note that reopening a local recent file re-prompts the file picker: for your security, the browser does not let a web app silently re-open a file from disk, so you confirm the file each time.
Every document has a set of properties (stored as front-matter), edited in the Properties panel: title, document number, revision, author, status, classification, and similar metadata.
The Insert Field feature drops a live document-property token into the body of your document — for example, the document number. The token displays the property's current value and updates automatically if you change that property. When you export, the field resolves to its value, so the PDF shows the real number rather than a placeholder. This keeps references like "Document {document-number}, Rev {revision}" always in sync with the properties.
Click Sign, type your name, and LX Draft records the signature in the document along with the date. Where a signature field is placed, the signature renders in a cursive font, for example:
Alex Morgan
For Lexis-controlled documents, signing uses your authenticated Lexis identity rather than a typed name. The release/version lifecycle in Lexis controls when signatures are locked and when they are cleared, so signing is tied to the formal project record rather than the honour system.
In standalone mode the revision history is a table you maintain by hand. Each entry has a class describing its stage:
| Class | Meaning |
|---|---|
| Draft | Work in progress. |
| Review | Submitted for review. |
| Approved | Reviewed and approved. |
| Released | Formally issued. |
| Obsolete | Superseded; no longer current. |
In Lexis mode the version history reflects actual releases recorded by Lexis — Lexis is the authoritative ledger. Creating a new version in Lexis strips the signing, bumps the revision, and unlocks editing so the next round of work can begin cleanly. You don't maintain the table by hand; it mirrors the real release record.
Every saved document carries a content hash — a fingerprint computed from its contents. This hash underpins two things:
While you edit, the document is a single continuous flow — there are no page boundaries in the editor. This is deliberate: it keeps writing and editing fluid, without text jumping around page breaks as you type.
Pagination happens at PDF-generation time. The export engine (PagedJS) flows your content into pages and applies the print furniture:
In the editor, footnotes are collected at the end of the document so they are easy to read and edit in one place. During PDF pagination, each footnote floats to the bottom of the page where its reference appears — proper paged-media footnotes. The reference itself renders as a superscript number in the body text.
Endnotes are different from footnotes: they are collected together at the very end of the document in the PDF, rather than per page.
LX Draft can export your document to several formats:
In every export, document-field and signature tokens resolve to their values, so the output shows the real document number, revision, signature, and so on — not the placeholder tokens.