Gutenberg + Themes: Week of November 1st, 2021

Hello! This is the 71st weekly roundup of theme-related discussions, fixes, and developments in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.

As always, please weigh in on the tickets below — your feedback is crucial and appreciated. 

Active Issues / Discussions & PRs

  • Themes: Consider changing some theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. settings to opt-out #36187 
  • Themes: Template Editing: Templates do not recognize theme template parts without a theme attribute #36124  
  • Themes: Navigation preservation plan #36087 
  • Themes: Themes should be able to provide default template for Template Editing via theme.json #36086 
  • Themes: CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. Custom Properties on BODY lead to DOM inheritance issues #35840 
  • Themes: Consider an FSEFSE Short for Full Site Editing, a project for the Gutenberg plugin and the editor where a full page layout is created using only blocks.-compatible approach to starter content #35680 
  • Themes: Allow themes to surface specific patterns from the Patterns Directory #35364 
  • Themes: Alternative approach to the layout outer padding #36214 
  • Themes:  BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor: pass assets through block_editor_settings_all #35950 
  • FSE:  FSE patterns are displayed in user’s language instead of site’s language #36227 
  • FSE:  Post Template returns empty string when no results found #36224 
  • FSE:  Discussion/i18n: Localising blocks in FSE themes #36061 
  • FSE: Add outer padding support to the flow layout #35919 
  • GS:  Theme.json – styles.blocks.coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./button.spacing.padding doesn’t apply if button uses Outline style #35438 
  • GS:  The margin added at the top level styles (for body) in theme.json is override by a margin added from gutenberg #36147 
  • GS:  Consider a root-level site padding solution that still lets some items go full-width #35607 
  • GS: Webfonts APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. implementation in theme.json #35591 
  • GS:  Fix: Crash when resetting user color palette. #36233 
  • GS:  Try additional CSS selectors for Button block styles #36130 
  • GS:  Allow switching global styles variations #35619 
  • GS: theme.json: adds a setting property that enables some other ones #36246
  • DT:  Duotone: Caching breaks duotones set through theme.json #36208  
  • DT: Post Comments Form: ensure typography styles are applied to child elements #36188 
  • DT: Consider changing some theme.json settings to opt-out #36187 
  • DT:  Navigation Block: Apply text-decoration support as CSS class #36104 


  • Themes: Navigation Area block #36178 
  • Themes: [Patterns]: Add a flag to hide patterns from UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. #36108 
  • Themes: Remove experimental feature notice #36083 
  • DT:  Font Family Support: Fix skip serialization check #36073 
  • GS:  Refactor theme.json migrations to be a single class #36182 
  • GS:  Update: Show all color and gradient origins (core, theme, and user). #35970  
  • GS:  Fix presets data for themes that do not provide any preset #36054 
  • GS  Adapt global styles code to use get global styles functions instead of low-level APIs #36075 
  • GS:  Update theme.json schema migrations #36154 
  • GS:  theme.json docs: add missing settings & styles #36137 
  • GS: Migrate theme.json v1 to v2 #36155 
  • GS:  Hotfix for leftovers of WP_Theme_JSON_Resolver::get_merged_data #36173 
  • FSE: Add fallback handling for plugins or themes using the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. #35877 

Overview Issues

  • Default Theme (Twenty Twenty Two): Overview of Gutenberg issues: #75
  • GS: The Global Styles Interface #34574  
  • FSE: Post Comments LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. Block: Tracking issue #34994 
  • FSE: Site Editing block placeholders #35501
  • DT: Typography Tools: Tracking defaults for blocks #35604
  • DT: Tracking: ToolsPanel Follow Ups #36165 

General Resources:

Please comment if there’s something you’d like to highlight 🙂