Introduction
If you've used modern web editors, you've likely encountered the block-based approach. From WordPress to Notion, the ability to add paragraphs, images, videos, and other elements as individual blocks has become a staple of content creation. The concept is simple and intuitive: click a button, choose a block, and it appears in your document. This design pattern has revolutionized how we build web pages, but it comes with a hidden cost: every platform reinvents the wheel.
The Problem: A Fragmented Block Ecosystem
While the / key has emerged as an informal standard for inserting new blocks, everything else remains proprietary. Each editor—be it a blogging tool, note-taking app, or content management system—builds its own blocks from scratch. Want a calendar block? A Kanban board? An interactive image gallery? You'll have to code it yourself.
This fragmentation hurts users. If someone uses your blogging engine, they're limited to the blocks you had time to implement. Those blocks might be basic or incomplete. Meanwhile, they see fancy blocks in WordPress, Medium, or Notion, but can't bring them into your editor. Blocks can't be shared or moved easily, and users are stuck with whatever features you managed to build.
The result? A walled garden of block types, where innovation is siloed and users lose out.
The Solution: The Block Protocol
To break down these walls, we're proposing the Block Protocol—an open, free, and non-proprietary standard that allows any block to work in any editor. Think of it as a universal language for blocks. If an application follows the protocol, it can embed any block from any provider, and vice versa.
The Block Protocol isn't a product or a company; it's just a set of rules for communication between embedding applications and blocks. By adhering to these rules, developers can write the embedding code once and instantly support a vast library of blocks.
How It Works
At its core, the protocol defines how a host editor should interact with a block. Blocks are self-contained components that receive data and expose actions (like rendering or responding to user input). The host sends configuration and content, the block renders itself, and they talk through a standard API. This makes blocks interchangeable and reusable across the web.
We've already released a very early draft of the Block Protocol and built some simple blocks and a demo editor. The goal is to foster an open-source community that creates a rich ecosystem of blocks—everything from simple paragraphs to complex Kanban boards.
Benefits for Everyone
Adopting the Block Protocol has clear advantages for all parties involved:
- For app developers: Write the embedding code once and immediately give your users access to thousands of block types. No need to reimplement every block from scratch.
- For block creators: Build a block once and have it work in WordPress, Notion, Medium, and any future editor that supports the protocol. Your block reaches a huge audience instantly.
- For end users: Enjoy a consistent, feature-rich block experience across different tools. You can take your favorite calendar block from one app and use it in another without hassle.
The protocol is 100% free and open. All sample code we develop will be open-source, so anyone can contribute or build upon it.
What Can Be a Block?
The beauty of the Block Protocol is its flexibility. A block can be anything that makes sense:
- In a document: paragraph, list, table, diagram, Kanban board, or even a structured data entry form.
- On the web: an order form, a calendar, a video player, or a live chat widget.
- For structured data: blocks that let you interact with typed data—think of a block that pulls in a product catalog from an API and lets users browse within the document.
This openness encourages innovation: anyone can create a new block type and share it globally.
Join the Movement
If you work on any kind of editor—blogging tool, note-taking app, content management system—consider adopting the Block Protocol. By doing so, you'll unlock a world of possibilities for your users. We invite developers, designers, and content creators to read the draft, experiment with our sample code, and help shape the future of web blocks.
Together, we can make the web better—one block at a time.