ianstormtaylor/slate

A completely customizable framework for building rich text editors. (Currently in beta.)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 13th, 2026
Created on June 18th, 2016
Open Issues & Pull Requests: 654 (+0)
GitHub issues: Enabled
Number of forks: 3,302
Total Stargazers: 31,748 (+0)
Total Subscribers: 294 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 89
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 901 days
Stale 30+ days: 89
Stale 90+ days: 88

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (155)
  • ⚑ cross platform (45)
  • improvement (25)
  • feature (14)
  • android (11)
  • question (4)
  • ♥ help (3)
  • discussion (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Slate is a completely customizable framework for building rich text editors. It solves the problem of editor schema inflexibility by implementing all logic through plugins, allowing developers to define custom content structures without being constrained by what the framework includes or excludes by default. Rather than hardcoding support for specific formatting like bold and italic, the tool lets you build editors that match your application's unique needs, whether that involves comments, embeds, or domain-specific content types.

Slate is designed for developers building sophisticated editors comparable to those in Medium, Dropbox Paper, or Google Docs. It works as a pluggable implementation of contenteditable built on React, giving you low-level control over editor behavior. The framework suits projects where you need deep customization and are willing to implement features yourself rather than relying on batteries-included defaults. The README acknowledges inspiration from Draft.js, Prosemirror, and Quill but does not make direct comparisons to these alternatives.

The project is in beta with a usable core API, though breaking changes may occur as the architecture evolves. The README explicitly states there is no finalized release schedule and that the project is contributor-driven rather than backed by a large company, meaning improvements depend on voluntary contributions from people who need them. The maintainers note that if you need something fixed or added, you should contribute it yourself or it may not happen, and they actively seek more engaged maintainers through their community channels.