barkdown

Every markdown WYSIWYG is two translators wearing one trench coat. The famous half, markdown to HTML, is a solved problem. The other half, walking an edited DOM back into markdown, is usually a bespoke function tested against whatever documents existed the week it was written, and it is the half that owns your data. barkdown makes that pairing the product: a codec whose DOM-to-markdown direction is guaranteed to invert marked's parse.

The contract is a property you can test rather than a promise you have to trust. For canonical input, a round trip is byte-identical. For any input, one round trip canonicalizes and a second is a fixed point. Footnotes round-trip precisely, and unknown elements pass through as raw HTML instead of vanishing. The suite enforces this with a fixture corpus, adapter conformance runs, and property tests that throw roughly two thousand generated documents at the invariant per run.

barkdown was extracted from Replicator's production blog editor, where every keystroke on every article crosses this exact boundary. It is the serializer half of an editable-markdown pipeline; woof-editor is the editing surface built on top of it.

bun add @kevinpeckham/barkdown marked marked-footnote

npm →GitHub →