LoginSign Up
← Back to all sparks
M

Meta Box

DEVOPS
Velocity6.3

WordPress custom fields and content-modeling framework for developers

metabox.io ↗

WordPress's custom-field layer is opening itself to agents and to native blocks.

wordpresscustom-fieldsagent-nativegutenbergdata-modelingno-code
◆Current state
Meta Box is the developer-leaning way to define custom fields, post types, and relationships in WordPress, sold as an all-in-one bundle. Its feed mixes product releases with tutorials, and releases arrive in bursts — a quiet spring, then three substantive posts since July. The recent ones are structural rather than cosmetic: an abilities layer that lets AI agents build and manage WordPress data from natural language, one-checkbox enforcement of one-to-one and one-to-many relationships, and block bindings that wire custom fields into Gutenberg blocks without PHP.
◆Where it's heading
Meta Box is repositioning from a PHP developer's toolkit toward a data layer other things drive. Block bindings remove the custom-block-and-shortcode step so site builders get dynamic data the way page builders always offered it; the abilities work does the same for agents, exposing the data model to natural-language instruction. The relationship and Block API v3 work underneath is the unglamorous half — a schema that is explicit enough about cardinality to be safely driven by something other than a human.
◆Prediction
The abilities surface is the one to watch: if agents can already create fields and models, the next constraint is permissioning what they are allowed to change on a live site. Expect scoping or approval controls before the feature is widely recommended for production.

◆Recent moves

  1. 19d ago

    Connect Meta Box Fields to Gutenberg Blocks with Block Bindings

    Meta Box fields can now be bound to Gutenberg blocks through WordPress block bindings, with no PHP, shortcodes, or custom blocks. It closes the gap with page builders on dynamic data and removes the most common reason a Meta Box site needed custom development.

    View source ↗
  2. 1mo ago

    New in Meta Box: Easier One-to-One and One-to-Many Relationships

    One-to-one and one-to-many relationships become a checkbox, enforced in both the admin UI and the API. Cardinality that was previously convention is now a constraint the data layer holds — the kind of tightening that matters once something other than a careful developer is writing to it.

    View source ↗
  3. 1mo ago

    Let AI Agents Build and Manage Your WordPress Data with Meta Box

    ⚡ SPARK

    Abilities expose Meta Box's data model to AI agents, so fields, models, and content can be built and managed from natural language. This is the move that reframes everything around it — the relationship and block-binding work becomes the schema an agent operates against.

    View source ↗
  4. 3mo ago

    How to Sync Terms to Posts

    A tutorial on syncing terms to posts using existing field, relationship, and filtering features. Instructional content rather than a release — the feed carries both.

    View source ↗
  5. 4mo ago

    Meta Box Update: Block API v3, Iframe Editor Support, Smart Allowed Blocklists, and More

    AIO 3.6 brings Block API v3, iframe editor support, and modal editing — compatibility work that keeps custom blocks functioning as the WordPress editor changes underneath them. Necessary groundwork for the block bindings that arrived four months later.

    View source ↗
  6. 7mo ago

    Block Editor - The New Field Type That Goes Beyond WYSIWYG

    A field type that puts the block editor inside a custom field, replacing WYSIWYG for structured rich content. An early step in the same direction as block bindings: treating blocks as the editing primitive rather than something Meta Box works around.

    View source ↗