Block-based Themes Meeting Agenda: May 5, 2021

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

Time: Wednesday, May 5, 2021, 10:00 AM EST

Channel: #themereview

Agenda

  • 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 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/
  • TT1 Blocks update
  • Continued discussion: Bridging the gap between existing themes and block-based themes
  • Open Floor / Q&A

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

+make.wordpress.org/core/ #agenda #meeting

Gutenberg + Themes: Week of Apr 19, 2021

Hello! This is the 46th 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/.  

Please weigh in on the tickets below — your feedback is crucial and appreciated.

Issues / Discussions & PRs

  • 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.: Verify if php template exists for a hybrid/universal theme with 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 parent 31123
  • Presets used in patterns: register them as user presets? 31124
  • (Optionally) rendering classic navigation data source in Navigation Block 30852
  • FSE: Add Disable FSE support flag. 30760
  • FSE: New milestone — Full Site Editing Gradual Adoption 30662
  • FSE: Finalizing the name and menu item placement proposal 29630
  • FSE Blocks: Add wrapper and align options to the Query block. 30804

Merged/Fixed

  • Hook maybe_inline_styles in the footer 31072
  • Global Styles: Make the config resilient to changes to safecss_filter_attr() 30888
  • Template part block – fix 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. notice for placeholder block. 30928

General Resources:

Thanks to @pbking for compiling this week’s update. Please comment if there’s something else you’d like to highlight! 🙂

#gutenberg-themes-roundup

Call for maintainers: Theme Unit Test

The Theme Unit Test is a widely known XML file with test content for WordPress websites. Theme authors and reviewers use this file to test various content types, including blocks, classic content, sound, video, images, comments, and menus.

As my focus is moving more towards accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and full site editing, I do not have the capacity to keep the file up to date or respond to issues and pull requests on GitHub in a timely manner.

Except for typos, the last substantial update to the theme unit test was July 3, 2020.

Because of the lack of updates, some 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. content no longer matches what you would get if you manually created new blocks in the editor. 

The demo content has been available since 2011 and is an important tool for theme authors. For it to remain useful, it needs to be updated more regularly, and your help is wanted.

What does a maintainer do?

  • Triage issues, open issues, and create pull requests on the 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/ repository.
  • Update the XML file when there are block markup changes (Keeping the old markup examples is still important for testing).
  • Update the XML file to include new major blocks.
  • Keep the codex page up to date.
  • Plan for the future and how the content and format can be improved.

What skills do I need to become a maintainer?

  • To update the file, you need to have basic knowledge of XML and the structure of the content exported and imported from WordPress.
  • Have intermediate experience with the block editor, and stay up to date with block markup changes.
  • You need a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account to be able to update the codex page.

I want to help, who do I contact?

Leave a comment on this post if you would like to help or if you have any questions.

Next Steps on Themes and Reviews

One of the action items from our call with Matt, was to come up with a list of non-negotiable guard rails for what could prevent a theme from being added to the repo. After some good discussions with him, I have a short list of guard rails but with the clarification that they shouldn’t prevent authors from submitting themes. Rather we should use the list to flag themes that have/don’t have each thing and show them in results accordingly. Likely exceptions to this would be proper licensing, adherence to fair use of the trademark, and a ban on child pornography or other images of anyone unable to provide consent.

To be very clear about the future state he’s asking for, let’s restate it.

Where we are headed

The human moderation process occurs post-commit and primarily for reported issues/spot checks. User preferences and experiences using a theme will drive the overall satisfaction ratings. Automated checks will assign quality or +/- flags for specific features and standards we wish to uphold. Those will all be weighted in an algorithm that shows preference for themes that meet the criteria.

For more context on the thinking behind this plan, check out the notes from Matt’s call with the Theme team. There are notes about what isn’t working, where others are succeeding that we could learn from, and a shared desire to host more themes in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ theme repo. 

What the team needs to get there

This concept is very different from where we are now, so it will be complex to accomplish. That being said, I think we can get most of this work managed by early 2022.  

What does the team need right now?

  • Access to their environment
    • @dd32 has already gotten this settled for @williampatton, but I don’t know if that’s a workaround or a sustainable solution. If it’s sustainable, we should help others get access as well.
  • Access to moderators tools
    • We assume this is the same moderator tools available to Support and Plugins, but it’s worth double checking. If yes, let’s ask for orientation materials and access. If no, let’s ask what it would take to replicate the system for Themes.

What is needed to get to post-commit checks?

  • Automated security checks (currently in progress with Dion)
  • Automated code scans (currently in progress with @dufresnesteven)
  • List of items to flag on themes (quality tags)
    • 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/ ready
    • Secure code
    • Up to date within the past 2-3 major releases
    • Translation ready
    • A11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) ready
    • Trademark usage
  • An algorithm 
  • A y/n voting mechanism for (user trust tags)
    • Is this theme up to date?
    • Are visual parts of this theme broken?

I’d like your feedback!

So far, there have been a few concerns raised about how we best move forward. I have listed them below, and welcome any thoughts about what we can change or create in our processes. If you have other thoughts about what I’ve missed, please also share those in the comments!

  • How will we help new authors feel confident in how to build themes?
  • How will we account for automated checks on 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?

Themes Team Meeting Notes – March 23, 2021

You can find the full meeting transcript on Slack (login required)

Meeting coordinator: @kafleg
Notes kept by @aristath

Weekly updates

Currently 56 new parent themes and 15 new child themes are waiting for review. Waiting time is currently 2 weeks.

In the past 7 days:

  • 310 tickets were opened
  • 326 tickets were closed:
  • 303 tickets were made live.
  • 19 new Themes were made live.
  • 284 Theme updates were made live.
  • 2 more were approved but are waiting to be made live.
  • 23 tickets were not-approved.
  • 0 tickets were closed-newer-version-uploaded.

Number of reviewers: 8

Discussion on Next Steps on Themes and Reviews

How will we help new authors feel confident in how to build themes?

@williampatton suggested to hold monthly meetings with new authors, guiding them and walking them through the process. This will help build confidence for authors, and hopefully result in higher quality themes. A post will be created asking for feedback about whether such an endeavor should be pursued or not.

@acosmin pointed out that in the Next Steps on Themes and Reviews post, the outlined goal is that “The human moderation process occurs post-commit and primarily for reported issues/spot checks”, which should also help with creativity.

Automated checks on 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 (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

automatic theme-checks will need to be modified for FSE themes. 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. can be checked with a modified subset of the current theme-checks, but 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. can’t be currently validated. The future of the repository as outlined in the next-steps post mentioned above relies more on user reports and reviews, so it’s more empowering for users and relies less on manual code reviews.

Open floor

@aristath mentioned a pull-request which was merged 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/. It’s a first step towards hybrid themes and allows using a mixture of PHP and HTML templates. Details about the implementation can be found in the pull-request’s description.