Block-based Themes Meeting Agenda: January 5, 2022

Welcome to 2022 everyone! Below is the agenda for this week’s 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 Themes meeting. This is the last meeting before WP 5.9 is released.

Time: Wednesday, January 5, 2022, 06:00 PM GMT+2

Channel: #themereview

Agenda

  • Discuss the remaining bugs that are impacting block-based themes for 5.9, including TT2.
  • What are theme developers looking forward to for the next stage of block theming?
  • Open Floor / Q&A

Please comment if you have any additional topics you’d like to see discussed!

+make.wordpress.org/core/ #agenda #meeting #block-based-meeting

Block-based Themes Meeting Agenda: December 8, 2021

After last weeks rescheduling, there will be a 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 Themes Meeting tomorrow. Below is the agenda;

Time: Wednesday, December 8, 2021, 06:00 PM GMT+2

Channel: #themereview

Agenda

  • Block-based theme updates 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/
  • Suggestions/Ideas for how Block Themes will work in the showcase after 5.9
  • Open Floor / Q&A

Please comment if you have any additional topics you’d like to see discussed!

+make.wordpress.org/core/ #agenda #meeting #block-based-meeting

Themes Team Meeting Notes – October 26, 2021

This is the meeting notes from the themes review team discussion, October 26, 2021. 

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

You can read the full transcript on our #themereview channel. This week’s meeting agendas can be found here. Thank you @kafleg for preparing the agenda. 

1. Weekly updates

The themes team published weekly updates about tickets and HelpScout emails.

See this week’s updates here in the past 7 days,

  • 290 tickets were opened
  • 312 tickets were closed:
  • 291 tickets were made live.
    • 33 new Themes were made live.
    • 258 Theme updates were made live.
    • 0 more were approved but are waiting to be made live.
  • 20 tickets were not-approved.
  • 1 tickets were closed-newer-version-uploaded.

Number of reviewers: 3

2. Discussion on 5.9 theme issues

With the 5.9 release is fast approaching, we’d like to share a couple of extra focuses on these Twenty Twenty-One theme issues.

There are several other issues that still need resolution. You can review those tickets having patches or submit patches if you can do that.

3. Open floor 

No questions or feedback related to the theme review were discussed during the open floor. 

[Next Steps on Themes and Reviews]

The theme review process is making steady progress towards automation. Here is the latest summary of the Theme tools and requirements recap posted by @poena

In case if you missed the ongoing efforts and upcoming changes, here are the links to follow. Feb 24, 2021 – Meeting Notes | Matt Josepha and Theme Team

#meeting-notes, #themereview, #themes-team

Block-based Themes Meeting Notes — Sept 1

When: September 1st, 2021

Where: #themereview

For the full conversation, here is a link to where the slack discussion starts.

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

We spent most of the meeting discussing two recent features particularly relevant to 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. themes:

1. Flex layout support: https://github.com/WordPress/gutenberg/pull/33359

  • For now, flex layouts can only be defined via theme (templates and some layout options in 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.), there is no 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. for setting a flex layout on a group block / container yet.

2. Adding a “gap” spacing around blocks globally: https://github.com/WordPress/gutenberg/pull/33812

  • A follow-on PR related to setting margins for first direct descents (:first-child) was raised: https://github.com/WordPress/gutenberg/issues/34441
  • There was some discussion around how the global gap and margin styles on the block should work together. The general consensus was the following behavior would be expected, from highest to lowest precedence:
    • Margin set by user in UI (eventually) – inline style
    • theme.json individual block margins
    • theme.json global gap
  • And if you want to keep following along, here is an overview issue about dimension controls: https://github.com/WordPress/gutenberg/issues/28356

Block Theme Resources created by Community Members

There have been some awesome block-theme resources recently created and shared by folks around the community! Here are a few highlights:

@Ellen wrote about her studio’s experience building their first block theme:  https://www.elmastudio.de/en/lessons-learned-building-our-first-block-theme-for-full-site-editing/

@poena published an in depth look at the typography options available in theme.json, filled with useful code examples to demonstrate: https://fullsiteediting.com/lessons/theme-json-typography-options/ and fullsiteediting.com is great for block related resources in general.

@richtabor came out with a 3 part series on standardizing how we build block themes. This is part 1 about everyone’s favorite — colors: https://richtabor.com/standardizing-theme-json-colors/

@karmatosed’s post was a great follow up alongside similar topic as the above — https://ephemeralthemes.com/2021/08/31/the-need-for-standardisation/

Please comment if you have any questions or notes to add!

#block-based-meeting

Summary of the request for feedback on requirement changes

At the end of July, the team published a request for feedback on proposed requirement changes.
We received feedback on how to improve the presentation and two suggestions for the removal of requirements.

The two requirements suggested for removal were:

  • The Theme URI and Author URI must not be the same.
  • Themes can use any language for text but only use one language.

There were no objections to these additional proposals, and the team will move forward with the requirement changes.

Please allow some time for us to update the relevant handbook pages and the automated theme review tools.

You can read all the replies to the post here:

#themereview, #themes-team