The Rise of Block-Based Editors

If you've written content online recently, you've likely encountered block-based editing. From WordPress to Notion, almost every modern writing tool organizes content into discrete units—blocks. You click a button (often a + or type a forward slash /) and a menu appears offering paragraphs, images, lists, embeds, and more. It's intuitive, visual, and has quickly become the standard for creating rich web content.

The Problem: A Tower of Babel

While the concept of blocks is now universal, the implementation is anything but. Every platform—WordPress, Medium, Notion, Ghost, and countless others—has built its own proprietary block system. Want a calendar block? A Kanban board? An interactive chart? You'll have to code it from scratch for each editor. End-users suffer the most: they become locked into the limited blocks their chosen tool provides, unable to easily transfer or reuse blocks from other platforms. This fragmentation stifles innovation and limits what creators can achieve.

Introducing the Block Protocol

To break down these walls, a new initiative called the Block Protocol has been proposed. It is an open, free, and non-proprietary standard that defines how blocks should communicate with the applications that host them. The core idea is simple: any block that conforms to the protocol can be embedded in any editor that also conforms to it. This decouples block creation from editor development, allowing a vibrant ecosystem to flourish.

How It Works

Imagine a world where you write a blog post in your favorite editor and embed a block that displays an interactive map, a real-time order form, or a video player—all without the editor needing to know anything about those specific blocks. The protocol handles the communication: the editor provides a sandbox environment, and the block runs inside it, sending and receiving data through well-defined hooks. Developers only need to write the embedding code once, and then any compliant block can be added instantly.

Benefits for Developers and Users

The Block Protocol promises to make life easier for everyone. For app developers, it eliminates the need to build and maintain an ever-growing library of blocks. They can focus on their core product and let the community provide the blocks. For block developers, they can write a block once and have it work across WordPress, Notion, Ghost, and any other editor that adopts the protocol. For end-users, it means access to a rich, interoperable library of blocks, regardless of which tool they use. Blocks become truly portable and reusable.

What Can Be a Block?

Almost anything that makes sense in a document or on a web page can be a block. Examples include:

• Content blocks: paragraphs, headings, lists, tables, blockquotes.
• Media blocks: images, galleries, videos, audio players.
• Interactive blocks: Kanban boards, calendars, order forms, diagrams, polls.
• Data blocks: charts, graphs, structured data from APIs.

The protocol also supports working with typed data, allowing blocks to interact with structured information like events, products, or people. This opens the door for rich, data-driven content.

Join the Movement

The Block Protocol is still in its early stages. An initial draft has been released, along with simple block examples and a reference editor. The goal is to build an open-source community that collaboratively creates a library of amazing, reusable blocks. If you develop editors, build blocks, or just care about the future of the web, now is the time to get involved. Visit the official site to read the draft and contribute.

By adopting a universal block protocol, we can unlock the full potential of web content creation—making it more flexible, powerful, and collaborative. Let's build a better web, one block at a time.