We write this blog with noteloom itself

This post, like every post on this blog, was drafted in the noteloom editor and exported straight to the page you're reading — no separate CMS, no copy-pasting into Markdown, no second tool.

That's the same og-image.png this site hands to every social network — dropped in here as a plain embed block, not a hardcoded <img>.

Why we bother

It's easy to claim an editor is reliable. It's harder to fake using it in public, every time, for real content. So instead of writing marketing copy about noteloom, we use it:

• Slash commands, headings, lists, callouts, quotes — all the blocks in this post came from the same "/" menu the Playground uses.
• The finished document is a plain JSON tree — the exact format described in the docs.
• That JSON is rendered to the static HTML you're reading right now via the same exportDocumentHTML export the editor exposes.

How this works, technically

A post here is a noteloom document (the same shape as a note or a Playground draft) checked into the site's source. At build time, the site spins up a headless noteloom store from that JSON and calls the package's HTML export — the result is plain semantic HTML, no client-side JavaScript required to read it.

If the editor can't produce a document good enough to publish on our own site, why would anyone trust it with theirs?

More posts — comparisons, guides, and behind-the-scenes notes on building noteloom — are coming, all written the same way.