Archived · LFM WG

Lossless Flavored Markdown

A named, versioned extended markdown flavor — and the shared remark/rehype package that backs it — so every Lossless site renders content the same way.

Part of: Tech Stack Deep Dives

All projects Edit on source

Why this exists

Across five+ sites we have five+ slightly different markdown pipelines — each fixing the same bugs in slightly different ways, each diverging a little further every month. LFM is the bet that:

A documented flavor lets authors know what syntax they can rely on.
A shared package means a citation bug fixed once is fixed everywhere.
A polyglot parser (directives + Markdoc + MDX-lite + Obsidian callouts → same node tree) means we don't have to fight authors about syntax.

What we're building

The @lossless-group/lfm published package (already shipping; consumed by mpstaton-site and now FullStack VC).
A formal spec — feature catalog with Stable / Beta / Wish List tiers.
A wish list backed by real authoring pain (highlights, wikilinks, auto-unfurl, slide separators).

Working group expectations

Authors tell us what they want to write; we figure out how to render it.
Renderers tell us what they want to receive; we figure out how to parse it.
The spec is a living document — read the LFM spec before bringing a new feature request.