A new open-source, in-browser rich-text editor library from the creator of ProseMirror and CodeMirror — a foundation developers build writing surfaces on.
Last verified · 2026-07-03 · by Moe Ameen
Wordgard is an open-source JavaScript library for building in-browser rich-text editors. It is not an app you sign into and start typing in — it is the foundation a developer uses to build a writing or editing surface inside a product, the same way ProseMirror, CodeMirror, or Lexical are. It was released as version 0.1 on July 2, 2026 by Marijn Haverbeke, who also created ProseMirror and CodeMirror, so it arrives with a rare amount of pedigree for a brand-new library.
Wordgard is best read as a ground-up redesign of the ideas behind ProseMirror, incorporating what Haverbeke has learned in the near-decade since ProseMirror stabilized, plus architecture borrowed from the CodeMirror 6 rewrite. It keeps ProseMirror's core premise — a semantic, schema-based document you define precisely, rather than free-form contenteditable HTML — but breaks compatibility to change how several things work under the hood: a simpler delta-style change model (keep / replace / update) in place of ProseMirror's "steps," node and mark types that are reusable across schemas, CodeMirror 6's facet-based extension system for plugin dependencies, and its own pointer- and keyboard-based selection handling instead of leaning on the browser. It listens to beforeinput events rather than diffing the DOM.
It is deliberately not a general-purpose "just give me a WYSIWYG box" widget. The point is control: you declare the exact content types your editor supports — text, tables, nested lists, figures — and the library gives you accessibility (screen readers, keyboard, mobile), right-to-left support, collaborative multi-user editing, and a functional-style programming interface to build on. The website notably advertises "0% AI"; Wordgard itself is not an AI tool and does not generate anything.
Be clear-eyed about maturity. Version 0.1 is early, self-described as unproven, with rough documentation and known mobile-browser touch-selection issues. Haverbeke expects to stay on 0.x releases for at least a year while the design settles, and advises against building on it yet if you need a stable library. It ships under the MIT license on what he calls an "abundance" funding model — prioritizing wide, unrestricted adoption. Treat every specific detail here as a launch-window snapshot of a fast-moving project.
Keep the layers straight and the fit is obvious. Wordgard is developer infrastructure — the thing under a writing surface, not the surface's output. What it helps produce, in the end, is text: the draft a person types into an editor built on it. And a draft is an input, not a finished content week. That is exactly where Kompozy picks up. Take the words — whether they came from a Wordgard-powered editor, a Google Doc, or a notes app — paste them into Kompozy, and it fans that single source into a real content package: a Blog Article, platform-native Text Posts tuned per network, a document-style Carousel, Quote Graphics, Infographic Photos, and an Email Newsletter, all held to one voice through your Persona Brief so nothing reads like it was rewritten five times.
The honest division of labor: Wordgard governs how you *write and edit* inside a product; Kompozy governs what happens to the writing *after* it's done — turning one draft into many on-brand formats and then doing the part no editor touches, scheduling and publishing across nine platforms plus blog and email from one queue with Autopilot and a per-post review pipeline. If you're a developer, you might even build the internal draft surface on Wordgard and route its output straight into Kompozy for production. Wordgard is where the words get shaped; Kompozy is where they become content and ship.
Wordgard is an open-source JavaScript library for building in-browser rich-text editors, released as version 0.1 on July 2, 2026 by Marijn Haverbeke, the creator of ProseMirror and CodeMirror. It is a foundation developers build editing surfaces on — not an app you sign into and write in — and it is a redesign of the ideas behind ProseMirror.
No. Wordgard is a new, from-scratch library by the same author that reworks ProseMirror's core ideas without compatibility — a simpler delta-style change model, reusable node and mark types, CodeMirror 6's facet-based extensions, and custom selection handling. Haverbeke has said ProseMirror is not being abandoned and will continue to be maintained.
No. Wordgard's own site advertises "0% AI." It is a rich-text editor library that provides the editing surface and document model; it does not generate text, images, or any content. It is unrelated to AI writing tools despite being a writing-related library.
Not on its own. Wordgard is developer infrastructure for building editors, so at most it produces the text someone types into a surface built on it. It has no content generation and no publishing. To turn a draft into finished posts across platforms you would use a content engine like Kompozy.
It is early. Version 0.1 is described by its author as unproven, with rough documentation and known mobile-browser issues, and he expects to stay on 0.x releases for at least a year. If you need a stable, battle-tested editor library today, Wordgard is not yet that; it is one to watch.