Building a WordPress Block Theme: Templates, Styles, and Accessibility
A WordPress block theme lets developers and site owners use blocks to edit every part of a site, including shared areas such…
Gutenberg 24.0 lets WordPress users try a redesigned settings panel for posts and pages. The redesign uses DataForm, a form-based way to display and edit settings such as an excerpt, featured image, author, or publication date. In 24.0, DataForm is an experiment you enable in the Gutenberg plugin, so its presence does not mean it has become the standard editor in WordPress.
If a plugin adds settings to the editor, test whether the new panel still shows and saves them. Compare it with the existing panel, then report the WordPress and Gutenberg versions you used and what happened. Developers can use those results as WordPress 7.2 approaches.
Use a non-production WordPress site or WordPress Playground. The Core team’s instructions require Gutenberg 24.0 or newer and identify WordPress 6.9 as a supported base for Gutenberg 24.0. Gutenberg trunk, the actively developed version, requires WordPress 7.0 or later.
Keep the plugin version separate from the WordPress version when you describe your results. WordPress 6.9 includes Gutenberg 21.9; WordPress 7.0 includes 22.6; WordPress 7.1 includes 23.6, according to the Gutenberg version handbook. Installing the Gutenberg plugin gives you a newer editor than the version bundled with those WordPress releases.
In the test site, open Settings → Gutenberg and enable Editor Inspector: Use DataForm. Open a post or page, compare its Post or Page settings tab with the experiment on and off, and reopen the item after saving to confirm that its values persisted. Record the WordPress and Gutenberg versions, active theme and plugins, user role, and experiment setting so someone else can reproduce the result.
DataForm replaces the classic summary panels in the editor’s Post or Page settings tab. The same form definition also powers Quick Edit in the Site Editor, where users edit content quickly. The shared design is intended to make settings more consistent in both places. Plugin developers should check each editor area where their settings appear.
Compare the same content with the experiment on and off. Look for settings that disappear or appear twice, and note any that move or change labels. Then change a value, save the post or page, and reopen it. Also test a custom post type, a WordPress content type whose registered features determine which settings apply. For example, a post type without excerpt support should not show an excerpt setting.
Check plugin-provided SEO and social settings, along with custom panels and editor extensions. Also test with different roles, such as an author, editor, and contributor. Check which controls each role can see and whether each role can save the changes it is allowed to make. Compare Quick Edit in the Site Editor separately; a shared form definition does not guarantee that every extension behaves identically in both places.
Check the version when you test extension APIs. The Gutenberg 24.0 testing call reports that PluginPostExcerpt was not ported and was deprecated in that version. It also reports that the editor.PostFeaturedImage and editor.MediaUpload filters did not work in 24.0. The call says both filters had landed in trunk and were expected in 24.1, though not in Quick Edit. Describe what you observe against the version you actually tested rather than treating a 24.0 limitation as a rule for later builds.
Extensions that rely on the old panels’ CSS classes or markup will not work with the new panels. The Core team recommends PluginDocumentSettingPanel for inspector content while the fields API remains in development. If a plugin control disappears, report the plugin’s name and version, along with where its control appeared before. Then describe how the control behaved with the experiment on and off. These checks show what to test, but they do not prove that a plugin is compatible.
The DataForm inspector is one part of a broader Gutenberg release. Released on September 16, 2026, Gutenberg 24.0 introduced changes to post titles in visual revisions. It also added a Grid layout for the Gallery block, with column and crop controls that can vary by viewport, plus an option for the Site Title block to resize its text to available width. The release notes also cover changes such as visible nonbreaking spaces and background images set from a URL.
For DataForm, focus on whether plugins remain compatible. The 24.0 notes also mention improvements to DataForm components, including a placeholder option for panel layouts and timezone communication in the date-and-time control. See the Gutenberg 24.0 release notes for the broader release details.
The September WordPress 7.2 roadmap lists DataViews and DataForms among the planned editor and extensibility work. The DataForm testing call describes consolidation of the inspector and Quick Edit as work aimed at stabilizing for 7.2, with a fields API also targeted for that release. These are roadmap goals, not guarantees that every feature will ship.
The roadmap also covers work outside the editor, including proposed security improvements, Notes, Global Styles, and additions to the block library. Treat these items as plans until release notes confirm they shipped. The 7.2 release tracker lists December 8, 2026, as the target release date; check the tracker for the latest schedule because release dates can change.
Ipsum is the proposed default block theme for WordPress 7.2. A block theme lets users build and customize site layouts with blocks. The theme’s announcement describes Ipsum as a minimal starting point, with style variations, typography pairings, patterns, and templates. It also says headers and sidebars remain optional and that its style combinations meet WCAG AA accessibility guidelines. Those claims describe the theme’s style combinations; they are not independent test results for every customized site.
To test Ipsum, activate it and inspect its style variations and patterns. Check the Index, Single Post, Page, 404, and Archive templates, then view pages with varied content at different screen sizes. The WordPress Test team’s checklist also asks testers to check PHP compatibility. Report which PHP version you used and what behavior you found. The testing information does not provide measured performance results or an independent accessibility audit.
The announcement initially presented Ipsum as a proposal, while later 7.2 planning materials describe it as the intended default theme. It is therefore more accurate to call it the planned default for 7.2 than to describe its inclusion as settled.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com