01
Source is sovereign
Ordinary editing avoids automatic formatting; explicit transforms produce a separate result and describe what changed.
About MDLoom
Markdown infrastructure should be calm, explicit, and dependable.
MDLoom exists because portable source deserves a professional workflow all the way through composition, conversion, print, and publication.
“Write in a declared Markdown profile; choose supported outputs with transformations and limitations visible.”
Why this product
Markdown is portable. Its surrounding workflow often is not.
A document can look correct in an editor and fail in the destination because its flavor, extensions, assets, and renderer were never declared. Rich exports add another layer: a DOCX, EPUB, and PDF each preserve different things.
MDLoom brings those contracts into the interface without making ordinary writing feel like configuration. The editor stays fast and familiar. Details appear when they prevent a compatibility error, protect a file, or explain an output.
The repository is organized as modular infrastructure that can be understood and tested. It is not currently presented as an open-source release; any future licensing or public collaboration decision will be made explicitly.
MDLoom does not create accounts or store user files on a server.
Principles
The standards we hold the product to
These are engineering and product constraints, not a marketing theme.
02
Standards are named
The current paths name a Markdown profile and available renderer identity. Full renderer, theme, sanitizer, diagram, and math version replay remains a production requirement—not an invisible-default promise.
03
Fidelity is specific
Exact source, visual pages, editable structure, best effort, and extraction are different promises.
04
Privacy is contextual
Local and server work are labeled before file selection, with limits and retention beside the action.
05
Accessibility is structural
Keyboard access, screen-reader semantics, compact layouts, and automated accessibility checks are release criteria; print glyph certification remains a production gate.
06
Useful beats numerous
A tool or page ships when it solves a real workflow and can explain its limitations—not to inflate a directory.
See the contract in the product.
Open anonymously, choose a Markdown profile, and keep source, preview, and diagnostics together.