Kjell Reigstad 1:40 pm on April 23, 2021
Tags:   

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

Carolina Nymark 1:14 am on April 22, 2021
Tags: , theme check,   

Removing blockers for block themes

This post is a proposal for how the themes team can continue reducing the theme directory requirements.

The problem: Blocked theme uploads

When a theme is uploaded to the directory, the files are checked by the Theme Check 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. If a theme fails some checks, the upload process is halted.
The checks in the plugin were created for classic themes, and some checks prevent 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 from being submitted to the theme directory without help from an admin.

Parts of full site editing are planned to be included in WordPress 5.8, and to make sure that end-users can test different full site editing themes, it needs to be easier to submit these themes to the theme directory.

Goals

This process has two short term goals:

  • Allow submission of themes that has support full site editing
  • Remove low impact requirements for all theme formats

Proposed solution

The first step is removing or reducing the severity level of some checks in the Theme Check plugin.

Examples:

  • CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. classes (Already in progress)
  • Tags and categories
  • Post navigation, pagination
  • Comments

Secondly, a flag needs to be created in the plugin to allow other checks to run selectively depending on the theme format. To do this, the plugin needs to be able to determine if the theme is a full site editing theme or not.
Related issues:
https://github.com/WordPress/theme-check/issues/297
https://github.com/WordPress/theme-check/pull/280

Once the plugin is updated, related pages on 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/ also needs to be updated to match this:
https://make.wordpress.org/themes/handbook/review/required/theme-check-plugin/
https://make.wordpress.org/themes/handbook/review/required/

The changes to the uploader also need to be combined with a call for full site editing themes, encouraging designers and theme authors to submit their themes.

If we need to discuss specific requirements in more detail, this can be done 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/ or during team meetings.

Proposed deadline

The planned release date of WordPress 5.8 is July 20, 2021. Considering the current review time, at the latest, the date for allowing full site editing themes in the directory would be June 20, 2021.

How to get involved

Initially, work will happen in the Theme Check GitHub repository and anyone is welcome to contribute. If you would like to hold a scrub and work on issues with other contributors, you are welcome to schedule one and host it in the #themereview 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/. channel.

Feedback

If you have any feedback on the proposed solution and deadline or other suggestions for how the team can work to remove the blocker, please comment below.

Thank you @kafleg and @aristath for reviewing this post.

#full-site-editing, #theme-check

Kjell Reigstad 8:30 pm on April 20, 2021
Tags: ,   

Block-based Themes Meeting Agenda: Apr 21, 2021

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

Time: Wednesday, April 21, 2021, 11:00 AM EDT

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
  • Universal Themes & Building Themes “between paradigms”
  • Open Floor / Q&A

@pbking will be facilitating this week’s meeting. Please comment if you have any additional topics you’d like to see discussed!

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

Kjell Reigstad 12:11 pm on April 16, 2021
Tags:   

Gutenberg + Themes: Week of Apr 12, 2021

Hello! This is the 45th 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.: Add Disable FSE support flag. 30760
  • FSE: Setting gradient as background does not match site editor view. 30768
  • FSE: What should replace the Theme Editor? 30695
  • FSE: New milestone — Full Site Editing Gradual Adoption 30662
  • FSE: Post Comments & Post Comments Form 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.: Provide HTML5 markup by default 30502
  • FSE: Discussion on Editor Styles Wrapper Padding for block themes 30545
  • FSE: Add post classes in the 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. https://codex.wordpress.org/The_Loop. 30497
  • FSE: Update customize link from Appearance menu for block themes 30643
  • FSE: Finalizing the name and menu item placement proposal 29630
  • FSE Blocks: Add wrapper and align options to the Query block. 30804

Merged/Fixed

  • FSE: Term Description block: Don’t output if there’s no description 30564
  • FSE: Fix template hierarchy fallbacks. 30599
  • Allow creating block templates in existing themes. 30438

General Resources:

Thanks @jeffikus for your help with this week’s summary. Please comment if there’s something you’d like to highlight 🙂

#gutenberg-themes-roundup

kafleg 2:22 pm on April 15, 2021
Tags: ,   

Themes Team Meeting Notes – April 13, 2021

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

Meeting coordinator: @kafleg
Notes kept by @kafleg

Weekly updates

Currently 46 new parent themes and 10 new child themes are waiting for review.
The waiting time is 3 weeks.

In the past 7 days,

  • 401 tickets were opened.
  • 417 tickets were closed.
  • 389 tickets were made live.
  • 23 new Themes were made live.
  • 366 Theme updates were made live.
  • 1 more were approved but are waiting to be made live.
  • 27 tickets were not-approved.
  • 1 tickets were closed-newer-version-uploaded.

Number of reviewers: 5

You can find more information here.

Changing the name of Theme Unit Test

There were some suggestions in 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/ for the possible name of Theme Unit Test. Among them, Theme Test Data was simplest and most reasonable suggestion by @kjellr. We finalized the name from the meeting. Now, Theme Unit Test will be Theme Test Data.

Project updates

Currently, there are 4 projects running,

  • Security testing tools for themes
  • Theme review action
  • Theme unit test
  • Requirements page review

We would like to request respected projects leads to provide the updates about the work. We were not able to take the updates during the meeting because none of the leads were present.

@kafleg is working on the requirements page review and he will consult with the themes team reps and try to reduce the requirements list.

Open Floor

During open floor, @joyously raised a question about using pre_get_posts in theme. She said, this seems to me to be 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 functionality. 

@kafleg replied, In most of the cases themes use pre_get_posts to exclude the categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. IDs in blog post. That might be the reason that you get 905 matches.

@greenshady said, Theme authors should mostly avoid pre_get_posts because most of the time this should be done via plugin. However, there are exceptions to this.  For example, a theme author might want to pull all the sticky posts into a slider at the top of the home/blog page.  And, because they wouldn’t want duplicate posts, it makes sense to hook into pre_get_posts to remove them from the main query.

You can read the entire conversation here.

At last, thank you all for your active participation in the meeting.

#meeting-notes, #themes-team