The Rise of Block-Based Editors
If you’ve used a modern blogging platform, note-taking app, or content management system recently, you’ve almost certainly encountered the “block” concept. Instead of a single text field, these tools present a canvas where each element—a paragraph, an image, a video, or an interactive widget—exists as a discrete block. You might be reading this inside WordPress, where a small + button reveals a long list of block types to insert. This design pattern has become nearly universal, appearing in tools like Medium, Notion, and countless others.
The appeal is clear: blocks offer a modular, intuitive way to compose and rearrange content. Users can mix text with rich media, tables, embeds, and custom components without wrestling with complicated markup. The / key has emerged as a de facto shortcut for inserting a new block, a rare moment of standardization across platforms. But beyond that simple keystroke, chaos reigns.
The Problem with Proprietary Blocks
Currently, every application that wants to offer blocks must build them from scratch. Want a calendar block? A Kanban board? An image gallery? You have to code it yourself. This leads to a fragmented ecosystem where each editor reinvents the wheel, and users suffer the consequences.
Imagine you write on a lesser-known blogging engine. You can only use the blocks that the developer had time to implement—often basic and incomplete. Meanwhile, you see a fancy block in WordPress or Notion that would perfectly suit your needs, but your editor doesn’t support it. Blocks become locked into their original platforms, unable to be shared or moved. Your creative possibilities are limited by the features your tool’s developers chose to recreate.
This non-standardization also stifles innovation. When every block must be built anew, developers spend time on duplicating existing functionality instead of creating novel, high-quality blocks. The end result: a poorer experience for everyone.
Introducing the Block Protocol
To break this cycle, we are proposing an open, free, and non-proprietary Block Protocol. Think of it as a common language that any block can speak, and any editor can understand. Once adopted, this protocol will allow blocks to be interchangeable and reusable across the entire web.
The protocol is not a product; it’s a set of conventions that any embedding application can follow. If a block conforms to the protocol, it can be used in any editor that also follows it—whether that’s a blog platform, a note-taking app, or a CMS. This eliminates the need for each editor to implement every block type from scratch.
We have released an early draft of the Block Protocol, along with sample blocks and a simple editor that can host them. The intention is to spark a community-driven initiative, with all sample code open-sourced under a permissive license.
How the Protocol Works
The Block Protocol specifies a minimal set of APIs and data formats that blocks and editors must agree upon. A block is a self-contained HTML element (often a web component) that communicates with its host editor through a defined interface. For example:
- Loading: The editor provides the block with initial data (e.g., text, settings).
- Saving: The block returns updated data when the user modifies it.
- Events: Blocks can signal state changes, resize, or request additional actions.
- Theming: A standard way for editors to apply styles without breaking block functionality.
By adhering to these conventions, a block developed for one protocol-compliant editor works seamlessly in another. No more “WordPress blocks only work in WordPress.” The editor writes the embedding code once and gains access to a potentially infinite library of blocks.
The Vision: A Universal Block Ecosystem
Our hope is to foster an open-source community that creates and curates a huge library of amazing blocks. Imagine:
- An order form block that collects payments, usable in any editor.
- A real-time collaborative Kanban board that slots into your note-taking app.
- A 3D model viewer for technical documentation.
- An interactive chart block that updates with live data.
Developers would write a block once and have it reach millions of users across different platforms. App makers no longer need to implement every feature; they can rely on the ecosystem. This accelerates innovation and gives end-users access to a richer set of tools.
What Can Be a Block?
The short answer: almost anything. Blocks can represent:
- Document elements: paragraphs, lists, tables, diagrams, code snippets.
- Web-native content: embedded videos, calendars, order forms, social media feeds.
- Interactive structured data: think of a block that lets you edit a spreadsheet, or a block that displays a sorted list of tasks from a database.
Essentially, any piece of content that makes sense in a document or on a web page can be a block. The protocol doesn’t limit creativity; it only provides the interface to plug blocks into editors.
Call to Action
If you work on any kind of editor—blogging tool, note-taking app, CMS, or even a custom webpage builder—you should consider adopting the Block Protocol. By implementing the embedding code once, you instantly enable your users to access a vast and growing library of blocks.
We invite developers, designers, and content creators to join the conversation. Visit the Block Protocol draft, try out the sample blocks, and contribute your own. Together, we can break the silos and make the web a more modular, flexible place—one block at a time.