The Fragmented State of Modern Web Editors
If you have published content online recently, you have likely encountered a block based editor. Platforms like WordPress, Notion, and Medium have all embraced the concept. You click a small plus button, and a menu of potential blocks appears, offering everything from standard paragraphs to complex image galleries and Kanban boards.
Users intuitively understand and enjoy this interaction model. However, while the industry has standardized on the concept of hitting the slash key to insert a block, the underlying technology remains entirely proprietary.
This lack of standardization punishes both developers and end users. Right now, every application that wants a rich editing experience has to build its block library entirely from scratch. If a software team builds a specialized calendar block for their specific content management system, it cannot be exported to a different note taking app. Users are artificially limited to whatever features the platform developers had time to build.
A Universal Standard for Reusable Components
Blocks should be interchangeable across the entire internet. The Block Protocol proposes a universal system that embedding applications can use to host any block type. If all platforms follow a unified protocol, a developer only needs to write the code for a specific block once.
The vision involves fostering an open source community to build a massive library of universally compatible blocks. This covers standard document elements like tables and lists, but more importantly, it opens the door for highly specialized data types. If a niche developer creates a block that perfectly visualizes the routing path between two airports, any platform supporting the Block Protocol can instantly embed it without writing additional integration code.
Machine Readable by Default
Beyond visual consistency, open blocks introduce a massive leap forward in data structure. Blocks can be strictly typed, making them automatically machine readable without requiring engineers to rely on fragile screen scraping techniques.
If a user creates an event block on a page, they can specify a schema that describes the event data in a universally understood format. Calendar applications can then instantly parse that web page, understand the event parameters reliably, and import the details. This eliminates the archaic practice of forcing users to download raw spreadsheet files just to access structured data.
Moving the internet toward highly structured, portable data components is a massive undertaking. The initial draft of the Block Protocol is currently at version 0.1, meaning it is still incredibly simple and requires significant iteration. Making the open web better requires early involvement from the community to test these concepts, provide feedback, and start building the next generation of web components.