WP Builds 458 – Unpacking the clever Content Area Block with Ian Svoboda
Feb 26, 2026
Ian Svoboda, a seasoned WordPress developer behind GenerateBlocks and the Content Area Block plugin, explains a tool that adds multiple editable content areas to templates. The conversation covers the plugin’s inspiration, technical hurdles with core APIs, real-world use cases like timelines, editor UX and width concerns, and hopes for future core integration.
AI Snips
Chapters
Transcript
Episode notes
Multiple Visual Content Areas Solve Editor Limits
- WordPress historically exposes a single post content area, which limits visual, template-specific editing for editors.
- Ian built Content Area Block to let templates host additional editable block outlets saved to postmeta and rendered elsewhere in the template.
News Timeline Need Sparked The Plugin
- A news client wanted a visual timeline area separate from main post content for editors to add years, months and events.
- Ian initially tried postmeta but decided a block-based timeline saved to meta would offer a much more visual editorial experience.
Post Content Is Just Another Storage Location
- The post_content column is just a string; conceptually post content and postmeta are both storage for block markup.
- By saving blocks to postmeta and rendering them via a template outlet, you can have multiple distinct editable block areas.