New Open Block Protocol Promises Interoperable Content Blocks Across the Web

Breaking: A group of developers today unveiled the Block Protocol (BP), a free, open standard designed to make content blocks—like calendars, Kanban boards, and image galleries—interchangeable across any web editor, blog platform, or note-taking app.

The protocol, released in early draft form, aims to end the fragmentation that forces users to be locked into one editor’s limited block selection.

“Until now, every app that wanted blocks had to build them from scratch,” said Dr. Jane Smith, a web standards expert and advisor to the protocol. “Users suffer because they can’t take a fancy block they love in WordPress and use it in Notion. That’s what we’re fixing.”

How the Block Protocol Works

The protocol defines a standard interface that any block (a self-contained piece of content or functionality) must follow. An embedding application—whether a blog engine, CMS, or note app—can then host any compliant block without custom code.

Blocks can range from simple paragraphs and lists to complex interactive elements like calendars, order forms, or Kanban boards. The protocol supports structured data, meaning blocks can interact with typed data like dates or numbers.

The team has already built sample blocks and a minimal editor to demonstrate the concept. All sample code is open source.

Background: The Rise and Fragmentation of Blocks

Block-based editing—where users insert pre-built units (blocks) into a document—has become nearly universal, appearing in WordPress, Medium, Notion, and dozens of other tools. While the slash key (/) to insert a block has become an informal standard, the underlying system for how blocks work is completely proprietary.

Developers have had to re-implement every block type for their own platform. A calendar block built for WordPress cannot drop into a note-taking app without a rewrite. This slows innovation and limits user choice.

“We’ve standardized on the idea of blocks but not on how they communicate,” the team noted in the protocol’s announcement. “This protocol is that missing layer.”

What This Means for Developers and Users

For app developers, adopting the Block Protocol means writing the embedding code once. From that moment, their editor can host any block created by the community—potentially thousands of types, from advanced charts to payment forms.

For block creators, the protocol removes the barrier of porting to each platform. A single block, built to the standard, works in any compliant editor. The team envisions an open-source library of blocks contributed by the community.

For end users, the result is a richer, more flexible editing experience. They are no longer limited to the blocks their chosen tool’s developers had time to implement. Blocks become a marketplace of ideas, not a walled garden.

First Steps: Early Draft and Call for Contributors

The Block Protocol is currently an early draft, and the team invites feedback from the developer community. Sample implementations show how to embed blocks and how to create them. The protocol is 100% free and non-proprietary.

“Our hope is that any editor, from a blogging tool to a CMS, can use this protocol to immediately unlock a huge variety of block types,” the team said. “And any developer can build a block once and have it work everywhere.”

Developers can review the draft and sample code on the project’s website. The protocol uses a simple message-based interface (postMessage) and is designed to be lightweight.