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

Themes Team Meeting Agenda for April 13, 2021

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.

If you want to join #themereview and contribute, check this link to get started.

We encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, April 13 2021, 15:00 UTC

Meeting agenda

  1. Weekly updates
  2. Changing the name of Theme Unit Test
  3. Project updates
  4. 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

Check regular weekly updates here.

Changing the name of Theme Unit Test

Changing the name of “Theme Unit Test” to some other name. There are few suggesions like,

  • Theme Acceptance Test
  • Theme Test Data
  • Theme Dummy Data
  • Demo Content
  • Test Site Content
  • Sample Theme Data

If you have any particular name suggestion, comment us below or use this GitHub link.

Project updates

Currently we are working on,

  • Security testing tools for themes – currently in progress with @dd32
  • Theme review action – currently in progress with @dufresnesteven
  • Theme unit test – currently in progress with @technocrews

We would like to request each project lead to provide us the updates via the comment section below.

Open Floor

We will discuss everything related to themes. Attendees can ask or share themes related things.

Please comment in the comment box below if you have anything to bring up during the open floor.

#meeting, #meeting-agenda, #themes-team

Block-based Meeting Notes — January 6

Channel: #themereview
Facilitated by @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 Highlights

  • Work on the “Archive Title” block is in progress. This (combined with the recent query 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. updates) will make archive pages very close to complete.
  • This PR would add a border radius control to the search block.

TT1 Blocks

Development for TT1 Blocks is on-going here: 
https://github.com/WordPress/theme-experiments/tree/master/tt1-blocks

  • The theme was recently renamed from “Twenty Twenty-One Blocks”, to avoid confusion with the original Twenty Twenty-One theme.
  • Progress in the repository’s project board is ongoing. There’s a growing list of blocker issues being migrated over to Gutenberg. @scruffian reiterated the prioritization of logging Gutenberg issues versus fixing them directly for now, so that the 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. team can get a clear view of all the outstanding tasks.
  • Progress on preparing the theme for its theme repository submission is happening in this issue.
  • There’s a related discussion around whether or not the theme should have additional code to fully support comments at this point.

Open Floor

  • @richtabor asked about the minimum Gutenberg version required for using TT1 Blocks. @kjellr want sure of the minimum required version, but suggested that since FSE is still under heavy development, anything other than the latest version might have breaking changes.
  • @richtabor asked if TT1 Blocks will work without 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. Once FSE functionality is merged into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. it will, but for now block based themes all require the plugin.

#block-based-meeting, #meeting-notes

Block Themes Meeting Notes for 16 December 2020

Channel: #themereview

Facilitated by @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 Highlights

  • WordPress 5.6 was released last week.
  • HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. blocks will soon have a font-weight setting
  • We want to load the Site Editor in an iFrame to give us a clean slate for styles in the front and back end.
  • Custom units are now an option for the spacing control.

There are more Gutenberg updates in the latest Gutenberg + Themes post.

Twenty Twenty-One (TT1) Blocks

Work is accelerating on the new 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. version of TwentyTwentyOne. This is centered around this project board.

The aim of this project is to reevaluate all of the Block specific CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. in TwentyTwenty one and determine if it’s still needed, and if it is, whether to move to Gutenberg; make it configurable via Global Styles, or add it to TT1 Blocks.

In many cases this is resulting in new issues and PRs in Gutenberg. We are keeping track of these on the board. Cards that are blocked by a Gutenberg issue should be moved to “Blocked” until the Gutenberg issue is fixed. This will give us a comprehensive list of all the issues we need to fix to get TT1 Blocks launched.

With the FSE Outreach Program starting up again soon, we’d like to add TT1 Blocks to the Theme Repository to make it easier for users to test Full Site Editing. We’ll use the name TT1 Blocks to ensure that users don’t get confused with the default theme TwentyTwentyOne.

Requirements for Block Themes

There was some discussion about the requirements for full site editing themes. The following changes were proposed:

  • Make the 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. file a requirement
  • Remove the requirement for specific php templates (e.g. header.php)

We need to ensure that the block markup in a theme submission is valid. Exactly how we go about this is something which still needs exploring.

Block-based Themes Meeting Summary: Aug 5, 2020

This week we held our bi-weekly 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 in the #themereview channel. The conversation starts here.

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/ Theme-related Updates

Keeping up with Gutenberg” was launched, a single place to follow Gutenberg related posts across the make blog universe. 

Discussion: porting existing themes to block-based themes

We had a discussion about easing the path for theme authors to make the switch to 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., by allowing block templates to work with existing php templates. Specifically, the group discussed how template resolution could work, and the challenges that will arise around how the site editor will handle pages that use existing php templates.

The discussion arose from this GitHub issue, and continues there.

Open Floor

  • “it is difficult to get an overview of what we are working towards”
  • “Is FSE still targeted to being stable, in core, in 5.6? Or stable in Gutenberg at the release of 5.6?”