Block-based Themes Meeting Agenda for June 17, 2020

Below is the agenda for this week’s Block-based Themes meeting.

Time: Wednesday, June 17, 2020, 16:00 UTC
Channel: #themereview

Agenda

  • Welcome
  • Status updates for 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 Theme efforts 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/:
    • Features and fixes in Gutenberg v8.3
    • In-progress issues and PRs to keep an eye on
  • Discussion
    • How should global styles support declaring fonts?
    • Calls for help / what are you working on?
  • Q&A / Open Floor

Please comment if you have any topics or demos you’d like to see covered in future meetings!

We also need a volunteer to take notes.

+make.wordpress.org/core/ #agenda

Updates to Theme Check

An update to the Theme Check plugin has been released.

  • Added escaping checks
  • Added tested up to and Requires PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. checks for the style.css
  • Added register_block_type to 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 territory check
  • Check for remove_action wp_head
  • Changed some checks from errors to warnings
  • Updated error messages
  • Updated regex for non printable characters
  • Fixed parse errors
  • Removed unused functions

For more details about the changes see the Github repository.

If you would like to contribute to Theme Check, issues and pull requests are welcome.

If you are experiencing problems with uploading your theme, you can open a issue on GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. We may need a copy of your theme to trouble shoot.

Gutenberg + Themes: Week of June 8, 2020

Hi everyone! Here’s the fifth 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/

Since conversations are ongoing, some of the issues & PRs mentioned were also present in previous weeks. We’ve tried to put brand new ones at the top of each of the bulleted lists. 

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

In progress / Discussions:

General

  • Simplify the Quote 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.’s editor markup to better match the front end. 22803
  • PR to adjust max-width setting for reusable blocks. 22632
  • PR for adding color controls to the list block. 21387
  • PR to change CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. specificity of default font-size rules. 22671
  • Fixes for the issue where custom theme colors don’t work in the editor after Gutenberg 7.9.1. 22356
  • An attempt to remove some of the extra canvas padding in the editor. 22213

Block-based Themes

  • Tracking issue for Template Tags in Full Site Editing 22724 
  • Syncing theme templates to the block editor in all contexts: 22469
  • Figuring out a way to handle inline dynamic content in theme templates. 21932

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.

  • HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites./CSS output not consistent. 22759
  • Last element in “Latest Posts” block has wrong right margin. 22911
  • FSE blocks are missing classnames on the front end. 21903
  • Site Title: Add support settings for colors, fonts, and line height. 23007

Global Styles

  • Recap and next steps for Global Styles. 22296
  • Tracking and consolidating style attributes for blocks. 22700 

Navigation

  • This board tracks Navigation Screen and Navigation Block issues that are important for the WordPress 5.5 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Project Overview

Merged:

General

  • New padding control to cover block. (21492, 23041)
  • New link color control to paragraph, heading, group, columns, and media-text blocks. (22722, 23025, 23049)
  • Experimental version of rich image editing tools. (21024, 22870)
  • Remove padding inheritance on lists in editor-styles (23080)

Block-based Themes

  • Add alignment and heading level support to the post title block. 22872
  • Add more customization options to the Author block. 22877
  • PR to add an “Export Theme” button to the Full Site Editor in the plugin. 22922  

Global Styles

  • A new iteration of `experimental-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.`, complete with draft documentation. 20290 (Documentation)

General Resources:


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

#gutenberg-themes-roundup

Meeting notes Tuesday 9 June 2020

Today we held a meeting with the proposed agenda. The recap of the meeting is below and you can read the meeting transcript in the slack archives (a Slack account is required).

Weekly Updates

In the past seven days

  • 251 tickets were opened
  • 250 tickets were closed:
  • 230 tickets were made live.
    • 15 new Themes were made live.
    • 215 Theme updates were made live.
    • 2 more was approved but are waiting to be made live.
  • 20 tickets were not-approved.
  • 0 ticket was closed-newer-version-uploaded.

We have managed to cut down on the queue length, which is always good news.

We thank to all the reviewers, keep doing a great job 🎉

Biweekly meeting schedule to Monthly meeting for Themes Team

Summer is closing in and we realised (and observed during the last few months) that having many meetings (regular, 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 and triages) can be a bit tiring – both to the reps and to the contributors.

The proposal is to cut the Themes Team regular meeting to once a month plus an additional one if we have some urgent thing to discuss.

This will give us a bit more breathing room both to recharge and focus on priorities set by phase three of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor development that are tied to the WordPress themes.

Open Floor

An issue was raised about Themes team not being a team anymore due to the lack of public discussions.

It was mentioned that the decisions are made and just announced.

This one is definitely on us (the reps). We should have been more tactful of how we presented the news (like changing the name of the team).
Team reps are always discussing and finding ways to improve this team’s impact in the WordPress community.

It’s hard to get noticed without active contributors, and in the last few years we have seen a decline in the active participants. To many authors theme repository is just one of the advertising avenues, which is disheartening.

One of the ways we wanted to spark the interest is to be involved with the core editor more, show that we are doing more than just review themes.

We definitely need to improve our transparency towards the community as team representatives. Writing more blogs about what we think would be a good way forward, and listening to advice and discussing them in the comments and then in the meetings.
What we do want to avoid are empty discussions that lead nowhere, as this is what kills the team. We need to adapt, change, and even innovate.

Andrea Middleton shared her experience from working in the Community Team:

In my observation, leading in the open is really difficult, and the process of learning how to do it effectively isn’t necessarily linear.

I’ve messed it up bunches of times — I think humans are just really prone to forming small groups, it helps us feel safe — and when it’s pointed out to me, I usually feel really dispirited and embarrassed.

For me, the best way to recover from that realization of “whoops, this conversation could/should have happened in the public channel” is to then go to the public channel and summarize the conversation there.

Andrea Middleton

It was also suggested that we should come up with a mission statement draft. Some goals that we as a team want to achieve.

This year we have put focus on Full Site Editing. We will continue working on preparing the community for the upcoming changes in the themes ecosystem.

Proofread by @williampatton

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

Theme Review Team Meeting Agenda for June 09

Theme review team (TRT) conducts a meeting on the second and fourth Tuesday of the month. Along with the fixed agendas, we have open floor meeting 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, 09th June 2020, 17:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Biweekly meeting schedule to Monthly meeting for Themes Team
  3. Open Floor

The discussion about the meeting agenda can be held in the comments below. You are encouraged to propose topics.

Meetings usually last around 60 minutes. Attend and share your valuable feedback and suggestions.

#meeting, #themesteam