Discofork
Repository brief

ianstormtaylor/slate

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T20:19:01.918Z
1mo ago

ianstormtaylor/slate

Slate is a beta, contributor-driven framework for building completely customizable rich text editors on top of React. It is actively maintained, widely used as an upstream project, and organized as a multi-package monorepo with docs, site, tests, and release tooling.

GitHub
Loading tags...
Stars31,610
Forks3,328
Default branchmain
Last pushed2026-03-26T22:59:09Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you need Discord’s custom editor behavior and are willing to own a stale, highly divergent Slate branch. If you want current Slate features, maintenance, and compatibility, upstream is the better base.

Prefer this fork only if you want an older, lightly maintained Slate snapshot for experimentation. If you want current editor fixes, release tooling, and ongoing maintenance, upstream is the better choice.

Choose this fork only if you need its older, customized Slate behavior and are prepared to maintain a large divergence yourself. If you want current Slate capabilities, active maintenance, or easier upgrades, upstream is the better choice.

Choose this fork only if you need an old Slate API/implementation and are prepared to maintain it yourself. If you want current Slate features, bug fixes, and tooling, upstream is the better choice.

Prefer upstream unless you specifically need this fork's custom behavior. This fork looks like an older, divergent editor branch with some tailored editing changes, but it is materially behind upstream and likely missing recent fixes, mobile/input polish, and maintenance work.

Prefer this fork only if you are inheriting an existing codebase or explicitly want its custom editor behavior. If you want current Slate maintenance, platform fixes, and easier upstream compatibility, upstream is the safer choice.

Prefer this fork only if you are locked to an old Slate architecture. For new work, upstream is far better: this fork is stale, highly divergent, and missing the modern package and release surface that current adopters expect.

Prefer upstream over this fork unless you specifically need an untouched historical snapshot. It adds no clear functionality and is materially behind current upstream maintenance.

Prefer upstream unless you specifically need this exact documentation snapshot. This fork adds essentially no product capability and is too stale for anyone depending on current Slate behavior.

Choose this fork only if you need its legacy, highly customized Slate behavior and are prepared to maintain it yourself. For most new adopters, upstream Slate is the safer choice because this fork is stale and significantly behind the active mainline.