Local-first Markdown editors
Use this page to evaluate Markdown tools by local-first authoring and portable product surfaces.
Local-first Markdown editors should be evaluated by more than whether they can open a Markdown file. The practical questions are storage defaults, offline behavior, preview policy, package reuse, extension boundaries, and how clearly sync or export crosses a user-controlled boundary.
| Criteria | MdWrk | Other local-first editors |
|---|---|---|
| Storage default | MdWrk centers browser-local workspace behavior for normal authoring. | Storage models vary by tool and should be inspected directly. |
| Package reuse | MdWrk documents reusable renderer, editor, theme, extension, and lander packages. | Many tools focus on app behavior rather than portable packages. |
| Public proof | MdWrk emits static content, sitemap, robots, LLM files, content indexes, and JSON-LD. | Public proof artifacts vary widely. |
Choose the editor whose boundaries match the workflow. MdWrk is strongest when local-first browser authoring and package adoption should work together.