Hello! This is the 47nd weekly roundup of theme-related discussions, fixes, and developments in Gutenberg.
Please weigh in on the tickets below — your feedback is crucial and appreciated.
Issues / Discussions & PRs
- FSE: Theme.json configurations with styles not expressed in a block’s block.json breaks FSE #31560
- FSE: Add a filter to determine whether a theme should use the Site Editor #31235
- Themes: Presets used in patterns: register them as user presets? #31124
- Themes: Substitute CSS Custom Property by the mechanism used in layout and duotone #31488
- Themes: Update the create a block theme tutorial #31269
- Themes: Optionally, rendering classic navigation data source in Navigation Block #30852
Merged/Fixed
- FSE: Show more Settings in Block Toolbar in Site Editor #31286
- FSE: Fix template loading order for child themes when no explicit template exists #31336
- FSE: Iframe the template editor #31375
- FSE: Post Content: Prevent infinite recursion #31455
- FSE: Unify the post tags and post categories block under a unique post terms block. #31458
- FSE: Block Library: Stabilize some theme blocks for WP 5.8 release #31423
- FSE & Themes: Split theme.css styles loading #31239
- Themes: Fix for template order logic bug introduced in 10.5 #31478
- Themes: Fix: Allow post comment button to inherit button & global styles automatically #31338
General Resources:
- Full Site Editing Milestones
- GitHub Issues: Full Site Editing
- GitHub Issues: Themes
- Block-based Themes Reference
- Block-based Themes Tutorial
- Experimental-Themes.json
- Using the Block Editor for Theme Parts
- Printing navigation-block HTML from a legacy menu in themes
Thanks @allancole for compiling this week’s summary. Please comment if there’s something you’d like to highlight 🙂