Gutenberg + Themes: Week of Oct 12, 2020

Hello! This is the 23rd 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. https://wordpress.org/gutenberg/

In case you missed it last week, be sure to check out this post about the near-term forecast for block-based theme functionality

Please weigh in on the tickets below — your voice and feedback are welcome! 

In progress / Discussions:

General:

  • Discussion about the “Theme Styles” writing option in the “Preferences” section. 26037
  • Color presets sometimes display differently between editor and frontend. 25889
  • Add border radius control to the search 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.. 25791
  • Load only styles for existing blocks on the front end. 25742

Block-based Themes

  • Suggestion that 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. template parts should not use text domain to detect the active theme. 25856
  • Full-site Editor: Try loading content in an iFrameiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. 25775

FSE Blocks

A set of blocks are available with the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to enable building templates in FSE.

  • Discussion about multi-column layouts in query blocks. 25462

Global Styles

  • PR adding font family option to Global Styles. 24868
  • PR adding font-weight option to Global Styles. 24978

Merged:

General

  • Columns Block: Add single column option. 24065
  • Add wide and full options to the Heading block. 25917

Overview Issues:

  • Full Site Editing Milestones. 24551
  • Template Tags in Full Site Editing. 22724 
  • Tracking and consolidating style attributes for blocks. 22700 
  • Missing query block functionality. 24934

General Resources:


Thanks to @itsjusteileen, @jffng, @joen, and @scruffian for help pulling this post together. Please let us know if it was helpful in the comments!

#gutenberg-themes-roundup

Meeting notes Tuesday October 13, 2020

Weekly Updates:

(the list includes both new tickets as well as updates too.
Current statistics can be found on https://themes.trac.wordpress.org/)

  • 264 tickets were opened
  • 268 tickets were closed:
  • 255 tickets were made live.
  • 30 new Themes were made live.
  • 225 Theme updates were made live.
  • 3 more were approved but are waiting to be made live.
  • 12 tickets were not-approved.
  • 1 ticket was closed-newer-version-uploaded.

Open Floor

  • Discussed moving the meeting time to an earlier time (see suggestion in the agenda comments). The suggestion generally received positive feedback from people in different timezones – including the Americas, Asia & Europe.
  • @joyously brought up the subject of quality control in premium themes, and how that is harmful to the WordPress ecosystem.
  • Feedback on this ticket for parsing theme readme files for the repository was requested: core.trac.wordpress.org/ticket/36971. Getting information from the readme files would be the first step to start redesigning the themes repository and be able to build something, so this needs to happen before we can move forward.

Themes Team Meeting Agenda for October 13

The themes team conducts a meeting on the second and fourth Tuesday of the month.

Along with the fixed agendas, we have an open floor at the end where you can ask or share anything related to themes.

We encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, October 13th 2020, 17:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Open floor

Weekly Updates

Current statistics can be found on: https://themes.trac.wordpress.org/ Themes TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket graph: https://themes.trac.wordpress.org/ticketgraph

Please comment in the comment box below if you have anything to discuss in the meeting.

#agenda, #meeting, #themes-team

Gutenberg + Themes: Week of Oct 5, 2020

Hello! This is the 22st 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. https://wordpress.org/gutenberg/

If you’re curious about the state of 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.-based theming, check out this post about the forecast for the next few months

Please weigh in on the tickets below — your voice and feedback are welcome! 

In progress / Discussions:

General:

  • Columns Block: Add single column option. 25867
  • Color presets sometimes display differently between editor and frontend. 25889
  • Add border radius control to the search block. 25791
  • Load only styles for existing blocks on the front end. 25742
  • Discussion: Should Gutenberg allow the use of a single-column columns block? 24711

Block-based Themes

  • Full-site Editor: Try loading content in an iFrameiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. 25775
  • Template part has a double wrapper. 25610
  • Add content-width option to 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.. 25160

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. Blocks

A set of blocks are available with the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to enable building templates in FSE.

  • Discussion about multi-column layouts in query blocks. 25462
  • Discuss how to allow the query block to inherit the global query. 25377
  • Consider not adding a self-link to the site-title block on the homepage. 25307
  • Allow using featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. as background for the Group block. 24660

Global Styles

  • PR adding font family option to Global Styles. 24868
  • PR adding font-weight option to Global Styles. 24978

Merged:

General

  • Heading Block: Allow wide and full alignments. 25917

FSE Blocks

  • Add CPT support in the Query block. 25903

Overview Issues:

  • Full Site Editing Milestones. 24551
  • Template Tags in Full Site Editing. 22724 
  • Tracking and consolidating style attributes for blocks. 22700 
  • Missing query block functionality. 24934

General Resources:


Thanks to @itsjusteileen, @jffng, @joen, and @scruffian for help pulling this post together. Please let us know if it was helpful in the comments!

#gutenberg-themes-roundup

Block-based Meeting Notes – Oct 7, 2020

Location: Make SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #themereview

Facilitator: @kjellr

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. https://wordpress.org/gutenberg/ + Themes Updates

  • An overview of FSE + block-based theming for 5.6 release was shared: https://make.wordpress.org/themes/2020/10/07/block-based-themes-and-wordpress-5-6/
  • Here’s a post about what’s new to Global Styles / theme.json: https://make.wordpress.org/themes/2020/10/01/gutenberg-9-1-new-json-structure-for-fse-theme-json-files/
  • Try this web-based GUI to generate a theme.jsonhttps://gutenberg-theme.xyz 
  • Twenty Twenty-One theme development is going strong! The 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.-based version is set to begin after BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 (Oct 20).

Discussion: which design tools should be enabled by default?

Gutenberg is building in a suite of design tools: https://github.com/WordPress/gutenberg/issues/20331. Some of these have already been implemented, and are available as theme options:

For these sorts of options, and upcoming ones like font weight, family, and expanded spacing controls, it would be helpful to get thoughts from theme authors about what should be enabled by default, versus having them be opt-in. 

Full discussion begins here, but here are some highlights:

@aristath shared:

For 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. themes they should all be opt-out IMO… enabled by default and if defined as false in the theme.json file then disabled.
Note: I’m referring to FSE themes, not “classic” themes

Several folks agreed with this view, but @greenshady raised an important counterpoint:

Design features that may interfere with theme styles need to be opt-in by default… When it comes to theme-supported features in general, I tend to lean toward an opt-in approach.  That gives themers the ability to explicitly make a choice.

Some of the discussion centered around whether add_theme_support should be used to control editor features:

I’m OK with going opt-out, but I don’t think we should misuse the theme supports system if it’s not genuinely meant to be a theme-supported feature. 

@kjellr summarized the discussion saying:

  • If a theme has 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., it seems ok to have these be opt-out. 
  • Otherwise, if the feature is expected to “just work” with themes without breaking something, it’s probably ok to enable it by default. Otherwise, they should be opt-in.
  • If these are “editor” features, and not something the theme needs to explicitly build in support for, then it may be confusing to use add_theme_support() for them. 
  • If users move between block-based themes and non-block-based themes, it will likely be confusing for seemingly unrelated features to turn on and off.

A follow on discussion ensued about how to make the distinction between block-themes and classic themes, in the themes directory and wp-admin.

@kjellr opened a meta ticket that could house the discussion between themes, meta, and design teams: https://meta.trac.wordpress.org/ticket/5465

#meeting-notes