In a move that could transform how content is created and shared online, a new open standard called the Block Protocol is being released today. The protocol aims to make it possible for users to embed the same interactive blocks—such as calendars, Kanban boards, or image galleries—across different blogging tools, note-taking apps, and content management systems without developers having to code them from scratch.
“Our goal is to make blocks interchangeable and reusable across the web,” said John Doe, the founder of the Block Protocol initiative. “Until now, every app that wants blocks has to implement them from scratch. That’s inefficient and limits what users can do.”
The proprietary nature of current block systems has left end users stuck with whatever blocks their chosen platform offers. “If someone is using my blog engine, they can only use those blocks that I had time to implement,” Doe explained. “Users might want a fancier block they saw in WordPress or Notion, but my editor doesn’t have it. Blocks can’t be shared or moved around easily.”
The Block Protocol, described as “open, free, and non-proprietary,” provides a universal way for embedding applications to integrate blocks. Any block written to the protocol can work in any compliant editor, whether it’s a blog platform, a note-taking app, or a CMS. The initial draft of the protocol has been released, along with sample code to demonstrate how it works.
Background
The block-based editor interface—where users click a “+” button or type “/” to insert content blocks—has become nearly universal. WordPress, Medium, Notion, and countless other tools all rely on blocks. However, each platform implements blocks in its own proprietary way.
While the shortcut to insert a new block (the “/” key) has been widely adopted, everything else remains fragmented. “We seem to have standardized on one thing: the / key to insert a new block,” noted Doe. “Everything else is completely proprietary and non-standard.”
This fragmentation means that developers must re-implement common blocks for every platform, and users are restricted to the features each editor provides. The Block Protocol seeks to end that by creating a universal standard.
What This Means
If the Block Protocol gains traction, developers will only need to write block code once and have it work across multiple platforms. “Anyone can develop a block once and have it work in any blog platform, note-taking app, or content management system,” said Doe. “It is all 100% free, open, and any sample code we develop will be open-source.”
For end users, this translates to a richer, more consistent experience. A block created for a to-do list or a video player could be used in WordPress just as easily as in a lightweight note-taking app, provided both support the protocol. The potential range of blocks is vast: “Anything that makes sense in a document—a paragraph, list, table, diagram—or anything that makes sense on the web, like an order form, a calendar, a video,” Doe elaborated.
The initiative is now calling on developers of editors and block authors to join the open-source community building a library of reusable blocks. “Our hope is that this will make life much easier for app developers to support a huge variety of block types,” Doe added.
Further details are available at the official Block Protocol website, where the early draft and sample implementations have been published.