docs/analysis/editor-architecture-candidates.md
This is the opinionated shortlist. Not a market map. Not a graveyard of every editor repo on GitHub. Just the candidates and inspirations actually worth keeping in Plate's future architectural comparison set.
It is intentionally not a prescription for exact features Plate should copy. The current analysis is strong enough to rank and frame the field, not to lock Plate into a shopping list.
Run this from /Users/zbeyens/git/plate if you want the comparison repos checked out in ..:
for repo in \
ProseMirror/prosemirror \
facebook/lexical \
ueberdosis/tiptap \
chenglou/pretext \
samwillis/premirror \
ianstormtaylor/slate \
inokawa/edix \
FormidableLabs/use-editable \
inokawa/rich-textarea \
ReactLibraries/markdown-editor \
urql-graphql/urql \
TanStack/db \
microsoft/vscode \
microsoft/language-server-protocol
do
name="${repo##*/}"
if [ -d "../$name/.git" ]; then
git -C "../$name" pull --ff-only
else
git clone "https://github.com/$repo.git" "../$name"
fi
done
Still the center of gravity.
Why it matters:
Take:
If Plate ever compares itself against one core editor architecture, this is the one. Everything else is either reacting to it, productizing it, or trying to escape its complexity.
The strongest non-ProseMirror engine to study hard.
Why it matters:
Take:
If Plate ever questions its underlying runtime model, Lexical is the real challenger, not a side-show wrapper.
Not the engine winner. The productization winner.
Why it matters:
Take:
Do not compare Plate to Tiptap as a better engine. Compare Plate to Tiptap as a better developer product.
This is the most important future-facing lane.
Why Pretext matters:
Why Premirror matters:
@chenglou/pretext as the measurement/layout primitive.../premirror direction is exactly the kind of synthesis worth watching: document engine plus deterministic page composition instead of pretending pagination is a CSS afterthought.Take:
This is not "another editor." It is the strongest path toward solving the unsolved page-layout problem on the web.
Important because Plate comes from this world.
Why it matters:
Why it is not the north star:
Take:
Study Slate to understand your inheritance and its limits, not because it is the future benchmark.
Very good inspiration repo. Not a core replacement candidate.
Why it matters:
contenteditable state manager.contenteditable is a mess.Take:
edix is a scalpel, not the next spine. Worth studying for lightweight surfaces, not for replacing Plate's serious document architecture.
Still one of the cleanest small-surface inspirations.
Why it matters:
Take:
This is not a full editor framework. It is a strong reminder that not every editable surface deserves the full Plate stack.
A very relevant companion to the edix line of thinking.
Why it matters:
Take:
Good inspiration for lightweight, high-polish text surfaces. Not a contender for Plate's core document model.
Narrower, but still useful.
Why it matters:
Take:
Relevant as a markdown-surface inspiration, not as a major architecture benchmark.
Not an editor. Still extremely relevant.
Why it matters:
Take:
This is useful when thinking about editor infrastructure, not text rendering.
One of the best non-editor inspirations on the list.
Why it matters:
Take:
If Plate wants better projections, indexes, or derived editor state, TanStack DB is a smarter inspiration than another random editor repo.
This is the service architecture model worth studying closely.
Why it matters:
Take:
If Plate ever grows semantic services, AI analyzers, structural linting, or document reasoning, this is the right mental model.
Important future platform primitive.
Why it matters:
contenteditable.Take:
Do not bet Plate on it yet. Track it aggressively.
More important than it looks.
Why it matters:
<input> and <textarea> behavior.Take:
This is not a framework. It is a signal about where the platform should go next.
For future architecture work, the real comparison set should be:
That is the serious shortlist.
Use these for tactical ideas, not for "should we rebuild Plate around this?":
Keep these in the room when designing next-gen Plate architecture:
This is not a mandate to copy them. It is a lens for what deserves deeper research when the question is architecture, layout, services, or future platform bets.
ProseMirror is still the architectural benchmark.
Lexical is the strongest engine challenger.
Tiptap is the best productization benchmark.
Pretext, especially combined with the ../premirror direction, is the most important future-facing bet because it attacks the layout and pagination problem that web editors still mostly fake.
The smartest non-editor inspirations are TanStack DB and the VS Code/LSP model.
edix, use-editable, rich-textarea, and @react-libraries/markdown-editor matter because they show how to build lighter editing surfaces without dragging a whole cathedral into every text field.