Supported file types
What DraftMesh does with .md, .html and .json files: which modes each supports, and which carry comments, suggestions, approvals and history.
DraftMesh lists and manages three kinds of files in a workspace. Everything else in the folder is left alone (and anything ignored by the folder’s ignore rules stays hidden).
| Type | Extension | What it’s for | Modes | Comments & suggestions | Approvals | History & sync |
|---|---|---|---|---|---|---|
| Markdown | .md | Prose documents — the heart of DraftMesh | Viewing, Suggesting, Editing, Code | Yes | Yes | Yes |
| HTML | .html | Rendered pages: dashboards, reports, business cases | Viewing, Code | Comments only | Yes | Yes |
| JSON | .json | Data files, typically feeding an HTML page | Viewing, Code | No | No | Yes |
Markdown documents
Full collaboration: all four modes, comments and suggestions anchored to any selection, approvals, version history, search, and sync. The file stays plain markdown that any editor can open.
HTML documents
An .html file renders as a real page inside a sandboxed frame — styles and scripts work, but the page can’t reach outside its sandbox. You can comment on the rendered content and approve the document; editing happens in Code mode. HTML pages can also read JSON data files from the same workspace and update live — see Data-driven pages.
JSON data files
A .json file opens as a collapsible tree in Viewing mode and as an editable text file in Code mode:
JSON files are data, not prose, so they deliberately carry no comments, suggestions, or approvals — but they are versioned like everything else, so history answers “who changed this number, and when”, and any version can be restored. DraftMesh refuses to save invalid JSON (from the editor or from an AI agent), so a typo can’t silently break the dashboards reading the file. A JSON file written invalid by an outside tool still opens — Code mode shows it with a notice so you can fix it.