Trade-offs · 2026-11 · 1 min read

Export is a projection, not a layout tool

Textrix will not try to be a desktop publishing app. Delivery happens through export — and that restraint is a feature, not a gap.

Illustration for: Export is a projection, not a layout tool

Sooner or later someone asks: if the editor can open Word files, why not let people lay out pages in them — fonts, margins, headers, the works? The answer is a rule, not a roadmap item: Textrix is where thinking happens; delivery goes through export.

Two different jobs

Layout is about satisfying a template: a journal style sheet, a report format, company letterhead. It is precise, finicky work with decades of dedicated tooling behind it — and none of it makes your notes better. Thinking is about connecting what you know. Mixing the two jobs in one file format is how you end up with a second copy of everything and no idea which copy is true.

Projections can be redone

An export to Word / PDF / HTML is a projection of the Markdown source — generated at the moment you need to deliver. If the projection is imperfect, you adjust the export and regenerate; the source never degrades. That is only possible because there is exactly one source.

  • Markdown stays the single source of truth
  • Word / PDF / HTML exports are generated on demand, at delivery time
  • A bad export costs a re-export, never a rewrite

What we deliberately did not build

No attempt at general-purpose Word layout: journals have their own templates, companies have house styles, and a knowledge-base tool that chases desktop publishing ends up good at neither. The boundary is stated in public on purpose — restraint written down is a commitment you can hold us to.

← All posts

Keep reading

Two more articles from the same trade-off series.

Still in development

Not yet available for download. Join the waitlist and you will be invited first when it opens.

Email-collection mode: submitting opens a pre-filled message in your mail client.