Block-based editors have taken the web by storm, appearing in everything from WordPress to Notion. But until now, each platform built its own blocks from scratch—wasting time and limiting users. The Block Protocol aims to change that by creating a shared standard. Below are answers to common questions. Click a question to jump to its answer.
- What is a block-based editor and why is it so popular?
- What problems does the lack of block standardization cause?
- What exactly is the Block Protocol?
- How do app developers and block creators benefit from the protocol?
- What kinds of content can be turned into a block?
- How can editors adopt the Block Protocol today?
- What is the current status and future of the Block Protocol?
What is a block-based editor and why is it so popular?
You've likely seen the plus (+) button in WordPress that reveals a list of content blocks—paragraphs, images, galleries, and more. This block-based user interface has become the standard for modern web editors, note-taking apps, and content management systems. The idea is simple: every piece of content is a discrete block that you can insert, rearrange, or remove. People love this approach because it makes content creation modular and intuitive. Instead of wrestling with a monolithic editor, you build pages block by block, just like stacking Legos. The popularity stems from its flexibility: you can mix text, media, and interactive elements without any coding. Most editors have even standardized on using the / key to quickly insert a new block. However, everything beyond that basic gesture has remained proprietary—until now.
What problems does the lack of block standardization cause?
Because every app implements blocks from scratch, users end up stuck with whatever blocks their particular editor offers. If you use Editor A, you get only the blocks that Editor A's developers had time to build—often basic or incomplete. Meanwhile, you might see a fancy Kanban board or calendar block in WordPress, Medium, or Notion that you wish you could use, but your editor doesn't support it. Blocks cannot be easily shared or moved between platforms. This non‑standardization forces end‑users to settle for limited features and prevents the web from having a rich, shared ecosystem of content components. Developers also suffer, constantly reinventing the wheel for every new block type. The core problem is that there is no open, universal way to package and embed blocks across different applications.
What exactly is the Block Protocol?
The Block Protocol is a new, open, free, and non‑proprietary standard designed to make blocks interchangeable across the web. Think of it as a common language that any embedding application (like a blogging tool or note‑taking app) can use to host blocks from any provider. By following this protocol, an editor can integrate any compliant block without writing custom code for each one. Similarly, block developers can create a block once and have it work in every editor that supports the protocol. The Block Protocol is still in its early stages—a draft has been released along with sample blocks and a simple editor to demonstrate the concept. The ultimate goal is for the protocol to become as ubiquitous as HTML itself, enabling a vibrant, open‑source library of reusable blocks that enrich the entire web.
How do app developers and block creators benefit from the protocol?
For app developers, adopting the Block Protocol means writing the embedding code just once. After that, their editor instantly gains access to a growing library of block types—from simple paragraphs to complex order forms—without extra development work. This eliminates the need to build and maintain blocks internally. For block creators, the benefit is equally clear: they can develop a block (say, a fancy calendar or interactive diagram) and publish it once under an open‑source license. That block then becomes available to any compatible editor across the web, reaching a huge audience. Both sides avoid duplication of effort. Because the protocol is free and open, anyone can contribute blocks or improve the specification. The Block Protocol fosters a community where innovation in block design is shared, not siloed, making the entire web more powerful and user‑friendly.
What kinds of content can be turned into a block?
Almost anything that makes sense in a document or on a web page can become a block. Common examples include paragraphs, lists, tables, diagrams, and Kanban boards. But the definition extends far beyond static content: a block can be an interactive calendar, a video player, an order form, or any component that works with structured data. The protocol is designed to support typed data, meaning blocks can define what kind of information they accept and produce. This allows editors to embed smart blocks that understand context—for instance, a contact form block that automatically maps fields to a contact schema. In essence, if you can imagine an element that belongs on the web, you can package it as a block following the protocol. The only limit is your creativity, and the open‑source community is expected to produce blocks for virtually every use case over time.
How can editors adopt the Block Protocol today?
If you develop any kind of editing tool—a blogging platform, a note‑taking app, or a content management system—you can start supporting the Block Protocol right now. The protocol is in early draft form, and the team behind it has released sample code and a simple reference editor. The first step is to understand the specification and implement the embedding interface. This typically involves adding a way for users to insert a block (e.g., via the plus button or slash command) and then rendering that block using the protocol's messaging system. Once that basic support is in place, your editor can host any compliant block without additional work. The documentation includes examples for common programming languages. Be sure to follow the official Block Protocol site for updates and to join the community discussion.
What is the current status and future of the Block Protocol?
The Block Protocol is currently in an early draft stage. The founders have released a proof‑of‑concept: a simple editor that can host a few basic blocks, along with sample block implementations. They are actively seeking feedback from the developer community to refine the protocol. The long‑term vision is to build an open‑source ecosystem of blocks—a library where anyone can contribute, share, and reuse blocks for any purpose. Future milestones include formalizing the specification, adding support for more advanced features like typed data, and encouraging major editors (WordPress, Notion, etc.) to adopt the standard. If the protocol gains traction, it could fundamentally change how content is created on the web, making blocks as portable and interchangeable as images or links are today. All sample code will remain open‑source, and the protocol will always be free to use.