Build a Content Platform / Editor

Anything where users write and collaborate: a blog editor, a docs platform, a content workspace, an LMS module. Tiptap and BlockNote handle the editor; the rest is your domain.

Repos

Layers

Build time

About 2 weeks

Outcome

See below

You will ship

A collaborative editor with slash commands, embeds, presence, and persistent storage.

How to feed this to your AI agent Browse the full directory

Editor

2 repos

ueberdosis

tiptap

Headless rich-text editor. Build any UI on top, extend with plugins.

Headless rich-text editor built on ProseMirror. ~28k stars. The default in 2026 for embedded editors in SaaS apps — Notion-style document ed…

facebook

lexical

Meta's editor. Fast, but less mature ecosystem than Tiptap.

Meta's extensible text editor framework. Used in Facebook and Instagram. More framework-y than Tiptap, steeper learning curve, more powerful…

Backend + persistence

1 repo

supabase

Realtime + Auth + Storage. Tiptap + Supabase Realtime = presence in a weekend.

Postgres + Auth + Storage + Realtime + Edge Functions in one open-source platform. ~73k stars. The fastest way to ship a backend in 2026 for…

UI scaffolding

2 repos

vercel

next.js

Server components for fast initial load with editor mounted client-side.

The React framework. ~128k stars. App Router is the bet — server components, server actions, edge runtime. 2026 sentiment is mixed: people l…

shadcn-ui

Toolbar, command palette, dialogs — all the chrome around the editor.

The default for Next.js builders in 2026. Not a dependency — you copy components into your codebase and own them forever. Built on Radix pri…

8 more layers · 11 more repos · members only

Forms + Schema1 repo
Block-style editors2 repos
Code editor inside content2 repos
Markdown / MDX2 repos
Realtime collaboration1 repo
Animation + interactions1 repo
Search inside content1 repo
AI in the editor1 repo

11 more curated repos · unlock full access · members only

Unlock with lifetime membership.

Pay once. Full directory unlocked forever. No renewals, no surprise charges.

See pricing

How to build build a content platform / editor with AI

The 4-step AI workflow

The AI agents are good at code. They're bad at deciding what stack to use. This bundle does the second part. You bring the agent.

1
Ideate with ChatGPT or Claude.ai (web)
Paste your idea: “I'm building build a content platform / editor. Help me sharpen the product spec — features, edge cases, MVP scope.” Iterate for 10-15 minutes until you have a clear one-page brief.
2
Pick your coding agent
For this kind of bundle, we recommend Claude Code — Sonnet 4.6/4.7 handles full-stack multi-file reasoning best. See the install guide → Cursor and Codex are also great; pick the one you already pay for.

Feed this bundle to the agent

Open Claude Code / Cursor / Codex in an empty folder, then paste:

I'm building build a content platform / editor. Use this bundle as the source of truth for the stack:
https://stackpicks.dev/build/content-platform

Brief from my product spec:
[paste your brief from step 1]

Follow the bundle order strictly:
  1. Editor
  2. Backend + persistence
  3. UI scaffolding
  4. Forms + Schema
  ...

Stop and confirm with me after each layer.

4
Wire one layer at a time, commit between each
Don't let the agent install everything before the first git commit. One layer = one commit. Catches drift early, easy rollback.

Beyond the bundle

1Ship the boring version first. The bundle above is the maximalist list. For an MVP, start with 60% of these and add the rest when real users ask.
2Deploy early. Push to Railway / Vercel after layer 02 (auth) — not after layer 09. Production breaks differently than localhost.
3Read CLAUDE.md / .cursor/rules in this repo for the project conventions your AI agent should follow.
4Iterate on the take. If a repo here doesn't fit your specific use case, tell us — contact — and we'll add a better one within 60 minutes.