# blog
WordPress 6.8: five changes theme developers should care about.
Five changes in WordPress 6.8 that matter for theme developers: Data Views API stable, section styles in theme.json, Interactivity API stable, block bindings expanded, zoom-out view default. Notes below reference the core release notes, the Gutenberg repository, and Rich Tabor coverage of the section-styles preview from 2025.
Five points.
- The Data Views API stabilised. Custom post type list tables can now be rendered via the block-editor Data Views component instead of the classic list-table PHP. Docs: developer.wordpress.org/block-editor/reference-guides/data/data-core-edit-site/. Practical impact: CPT admin UIs feel like the site editor.
- Section styles landed in
theme.json. You can now define reusable style variations at the section (Group) level, not just at the block level. Example:styles.blocks.core/group.variations.dark. Multiple sections on one page can pick from a named palette. - Interactivity API moved to stable. Themes and plugins that need small interactive components (accordion, tabs, live filter) can now use the WordPress-provided Interactivity API instead of shipping Alpine.js or vanilla JS glue. Ships zero extra JS on pages that do not use it.
- Block bindings expanded to cover custom fields on any block. Bind a paragraph block to a post-meta key via
metadata.bindings.content. Removes the need for shortcodes or ACF blocks for simple meta rendering. - Zoom-out view for the site editor is now the default when editing patterns. Editors see the whole template at once, drag patterns to reorder. Rich Tabor covered the earlier iteration on rich.blog; the 6.8 default-on shift is confirmed in the WordPress core release notes.