ianstormtaylor/slate

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.