Discussion: Request for feedback on requirement changes

Please take the time to read the following proposal for updated theme directory requirements,
and help out by answering the questions at the end of the post.

This post is an early proposal, and the team representatives are looking for your feedback and help with improving it.

Before answering the questions, please read about the background to the changes to the requirements.

Would you please submit your comments by July 26, 2021?

On July 28, 2 pm CET, the team will conduct a zoom interview with theme authors about the requirements.
The spots are limited; please leave a comment on the post if you would like to participate.
If needed, we can schedule more than one call.

The requirements are available in two formats: the text below, and presented in this table in the theme requirements GitHub repository.


1. Licensing & copyright

Themes must be compatible with the GNU General Public License

Although any GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples.-compatible license is acceptable, using the same license as WordPress — “GPLv2 or later” — is strongly recommended.

All code, data, and images — anything in the theme zip file — must comply with the GPL or a GPL-Compatible license.
Included third-party libraries, code, images, or otherwise, must be compatible.
For a specific list of compatible licenses, please read the GPL-Compatible license list on gnu.org.

  • Include copyright information for the theme itself.
  • Include license, copyright information, and source for all resources included, such as fonts or images (For assets in the public domain, copyright information is excluded).
  • Provide a list of all resources in one file.
  • All code and design must be your own or legally yours. Cloning of designs is not acceptable.
  • Copyright statements on the front end must only display the user’s copyright, not the theme author’s copyright.

    Read more about copyright and attribution.

2. Privacy

Any tracking and collection of user data must be disabled by default and opt-in only.
Documentation on how any user data is collected and used needs to be in the theme readme.txt file, preferably with a clearly stated privacy policy.

3. 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)

Skip links
Themes must include a mechanism that enables users to navigate directly to content or navigation on entering any given page.

These links may be positioned off-screen initially but must be available to screen reader users and must be visible on focus for sighted keyboard navigators.

A minimally conforming skip link must:

  • Be the first focusable element perceived by a user via a screen reader or keyboard navigation
  • Be visible when keyboard focus moves to the link
  • Move focus to the main content area of the page when activated

Notes: This only applies if there is something to skip past, such as a menu or larger 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. section or secondary widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. area before the main content.
In 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, skip links are added automatically to the 

 element.

Keyboard navigation
Theme authors must provide visual keyboard focus highlighting in navigation menus and for form fields, submit buttons, and text links.

  • All controls and links must be reachable using the keyboard.
  • All controls usable with the mouse must be usable with the keyboard, regardless of device and screen size. Including but not limited to responsive versions for small screens, mobile and other touch screen devices.

Further reading about keyboard navigation

Links within content and comments must be underlined
When links appear within a larger body of block-level content, they must be clearly distinguishable from surrounding content (Post content, comment content, text widgets, custom options with large blocks of texts).

Links in navigation-like contexts (e.g., menus, lists of upcoming posts in widgets, grouped post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data) do not need to be specifically distinguished from surrounding content.

The underline is the only accepted method of indicating links within the content. Bold, italicized, or color-differentiated text is ambiguous and will not pass.

If the theme has the tag ‘accessibility-ready’ then it needs to meet these additional requirements.

4. Code

There must not be any 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. or JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. errors, warnings, or notices.

The theme must be secure.

  • Validate and sanitize untrusted data before entering it into the database.
  • Escape all untrusted data before output (See: Data Validation).

Do not use deprecated functions or constants.

Prefix
Provide a unique prefix for everything the theme defines in the public namespace, including options, functions, global variables, constants, post meta, wp_enqueue_script/style handle names, add_image_size names, wp_script_add_data keys, slugs/ids for new categories created with register_block_pattern_category etc.

Exceptions:

  • wp_enqueue_script & wp_enqueue_style handles should not be prefixed if they are 3rd-party assets, like a framework’s CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. files or any 3rd-party script.
  • Menu locations and sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. IDs.

5. Functionality and Features

Manipulating the preview 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/ is not allowed and can result in suspension or your user account being terminated.

Admin notices:

  • Use the admin_notices API for all notifications generated by the theme.
  • Notices must be dismissible.
  • Everything wrapped in the admin notice must follow coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. design for notices.

Do not:

  • Place WordPress features behind a paywall
  • Remove, hide, or otherwise block the admin bar from appearing
  • Redirect on theme activation or modify the activation process
  • Remove non-presentational hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.

Do not include:

  • Custom post types
  • Custom blocks
  • Custom roles
  • Custom user contact methods
  • Custom mime types
  • Shortcodes
  • Functionality that is not related to design and presentation
Examples of non-presentational hooks
'wp_generator', // @link https://developer.wordpress.org/reference/functions/wp_generator/
'feed_links', // @link https://developer.wordpress.org/reference/functions/feed_links/
'feed_links_extra', // @link https://developer.wordpress.org/reference/functions/feed_links_extra/
'print_emoji_detection_script', // @link https://developer.wordpress.org/reference/functions/print_emoji_detection_script/
'wp_resource_hints', // @link https://developer.wordpress.org/reference/functions/wp_resource_hints/
'adjacent_posts_rel_link_wp_head', // @link https://developer.wordpress.org/reference/functions/adjacent_posts_rel_link_wp_head/
'wp_shortlink_wp_head', // @link https://developer.wordpress.org/reference/functions/wp_shortlink_wp_head/
'_admin_bar_bump_cb', // @link https://developer.wordpress.org/reference/functions/_admin_bar_bump_cb/
'rsd_link', // @link https://developer.wordpress.org/reference/functions/rsd_link/
'rest_output_link_wp_head', // @link https://developer.wordpress.org/reference/functions/rest_output_link_wp_head/
'wp_oembed_add_discovery_links', // @link https://developer.wordpress.org/reference/functions/wp_oembed_add_discovery_links/
'wp_oembed_add_host_js', // @link https://developer.wordpress.org/reference/functions/wp_oembed_add_host_js/
'rel_canonical', // @link https://developer.wordpress.org/reference/functions/rel_canonical/

6. Plugins

Themes may only recommend plugins that are hosted on WordPress.org.

Plugins may only be installed by user action, not automatically.

Do not:

  • Include zip files or plugins in the theme folder, or download plugins automatically.
  • Include 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.

If you are not sure if a feature is plugin territory, contact the team and ask first. themes@wordpress.org.

Examples of plugin territory
Analytics or tracking support
SEO options
Contact forms
Non-design related meta boxes
Resource caching
Social media ‘like’, ‘follow’ and ‘share buttons’
Session tampering

7. Naming, spelling, and trademarks

The themes team can decline themes based on the name and request that the name is changed if they decide that the name is inappropriate or too similar to an existing theme or brand.

  • Theme names must not use: WordPress, Theme, Twenty*
  • Spell “WordPress” correctly in all public-facing text: all one word, with both an uppercase W and P
  • No violation of trademarks.

8. Language & internationalization

All text strings must be translatable using gettext, with the temporary exception of text in 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. template files.

Use the theme slug as the text-domain and add it to style.css.
The theme slug is the name of the theme in lower case, with spaces replaced by a hyphen (-).
It is also the folder name for the theme.

If the theme uses a framework, then no more than two unique text domains may be used (like tgmpa, redux-framework, kirki, or some other allowed framework)

Themes can use any language for text but only use one language.

Read more about internationalization.

9. Files

Prepare your files:

  • Themes must be complete at the time of submission.
  • Remove code not intended for the free version of the theme.
  • Remove directories such as .git, .svn, .hg, and .bzr.
  • Make sure that only one type of line ending is used. If both DOS and UNIX line endings are used, this can cause problems with SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/., and your theme or theme update will not be uploaded to the directory.
  • If your theme is based on a starter theme like Underscores (_s), make sure that all files are updated correctly.
Files that are not allowed
thumbs.db          =>  Windows thumbnail store
desktop.ini        =>  windows system file
project.properties =>  NetBeans Project File
project.xml        =>  NetBeans Project File
.kpf               =>  Komodo Project File
php.ini            =>  PHP server settings file
dwsync.xml         =>  Dreamweaver project file
error_log          =>  PHP error log
web.config         =>  Server settings file
.sql               =>  SQL dump file
__MACOSX           =>  OSX system file
.lubith            =>  Lubith theme generator file
.wie               =>  Widget import file
.dat               =>  Customizer import file
.xml               =>  XML file
.sh                =>  Shell script file
favicon.ico        =>  Favicon

Hidden Files or Folders
Zip files

Allowed xml files:
wpml-config.xml,loco.xml,phpcs.xml',

No remote resources are allowed without user consent:

Include all scripts, images, videos and other resources in the theme zip file. The only exception to this requirement is Google Fonts.

Do not:

  • Use CDN or similar services
  • Fetch any files or data from a remote resource, including your websites, without the user’s explicit consent.

This is because of GDPR and privacy requirements.

Updated July 25: Typo fixed.

Main stylesheet

The headers in style.css need to follow the guidelines and requirements for the main stylesheet in the Theme Developer Handbook.

Required headers in style.css
Theme Name: Name of the theme.
Author: The name of the individual or organization who developed the theme. Using the Theme Author’s wordpress.org username is recommended.
Description: A short description of the theme.
Version: The version, written in X.X or X.X.X format.
Requires at least: The oldest main WordPress version supported, written in X.X format.
Tested up to: The last main WordPress version the theme has been tested up to, i.e. 5.4. Only the number.
Requires PHP: The oldest PHP version supported, in X.X format, only the number
License: The license of the theme.
License URI: The URL of the theme license.
Text Domain: The string used for textdomain for translation.

Theme URI is optional. If used, it must be about the theme we’re hosting on WordPress.org.
Using WordPress.org in the Theme URI is reserved for the default themes (Twenty X).

Author URI is optional. If used, it must be a page or website about the author, author theme shop, or author project/development website.

The Theme URI and Author URI must not be the same.

For a list of available tags, see Theme Tag List.

Readme.txt file

A valid readme.txt file must be included.

readme.txt example
=== Theme Name ===
Contributors: (Should only contain one WordPress.org username.)
Requires at least: 5.0
Tested up to: 5.2
Requires PHP: 5.6
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Short description. No more than 150 chars.

== Description ==
Theme desc.

== Frequently Asked Questions ==

= A question that someone might have =

An answer to that question.

== Changelog ==

= 1.0 =
* Added new option

= 0.5 =
* Security bug addressed
* Changed thumbnail size

== Upgrade Notice ==

= 1.0 =
* Upgrade notices describe the reason a user should upgrade.  No more than 300 characters.

= 0.5 =

* This version fixes a security related bug.  Upgrade immediately.

== Resources ==
* magnify.jpg Jane Doe, CC0, example.com
* supermenu.js © 2013-2015 James Today, MIT, example.com

 

Stylesheets and scripts

When minified scripts or files are used, the original files must also be included in the theme folder.

Use of third party libraries
WordPress includes a number of libraries such as jQuery. For security and stability reasons, themes may not include those libraries in their own code. Instead, themes must use the versions of those libraries packaged with WordPress.

For a list of all JavaScript libraries included in WordPress, see Default Scripts Included and Registered by WordPress.

Images

Images that promote hate or violence or images that show children with recognizable facial or body features are not permitted.

Screenshot

  • The screenshot must not look like an advertisement. The reviewer can subjectively ask you to change screenshots if they find that it is not appropriate.
  • The screenshot must not be bigger than 1200 x 900px
  • The ratio of width to height needs to be 4:3

10. Classic themes

Have a valid DOCTYPE declaration and include language_attributes().

Call custom template files using get_template_part() or locate_template().

Display the correct content according to the front page setting (See explanation).

Options and Settings
Use the Customizer for implementing theme options.

Use edit_theme_options capability for determining user permission to edit options, rather than relying on a role (e.g., administrator) or a different capability (e.g., edit_themes, manage_options).

Include:

Templates
If used in the theme, standard template files are required to be called by their respective function.

11. Block themes

Include required files: Index.php, style.css, readme.txt, 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., and index.html.
Index.html needs to be placed inside a folder called block-templates.

Block templates must be complete, and blocks may not have missing or incorrect closing tags.

12. Selling, credits, links, and spam

Themes can include one single front-facing credit link, which is restricted to the Theme URI or Author URI defined in style.css.
Themes can also have an additional front-facing credit link pointing to WordPress.org.

  • Themes must not display obtrusive upselling
  • Themes must not display upselling on the front

Themes must disclose all affiliates.

The theme and its public-facing pages, including theme description, readme files, bundled starter content, and translation files, may not be used to spam. Spammy behavior includes (but is not limited to) tags to competitors’ products, blackhat SEO, and keyword stuffing.

13. Theme author and theme upload restrictions

Only submit one new theme at a time. You can submit unlimited updates for your existing themes that are in the theme directory.

Theme names cannot be “reserved” for future use.

Intentionally attempting to exploit loopholes in the guidelines may lead to suspension.

Licensing of themes distributed outside the theme directory
If you distribute themes, you may only distribute themes that are 100% compatible with GPL.
Otherwise, you can not add themes to the WordPress.org Theme Directory (See explanation).

Example: If you have a Themeforest account and you’re selling themes on it, all those themes need to state on their sales page that they are 100% GPL compatible (Info).

Your site needs to state that the products you’re selling/distributing (free and paid) are GPL compatible. It needs to be in an easy-to-find place for visitors.

Multiple Theme Author Accounts
You can have multiple accounts with the following restrictions:
You can’t have more than one (1) open ticket in any of the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. reports/queues or under review. That means you can’t have one (1) theme ticket from an account and another one from a secondary account simultaneously open in any of the queues.

Failing to respect the above requirement will result in the closing of all tickets and not having the possibility to upload those themes again. Also, a one (1) month no upload possibility for each ticket closed. Depending on the severity of the case, you might also end up with a permanent ban on all your accounts.

To avoid penalties, the team requests that you disclose all your accounts by emailing us at themes[at]wordpress.org.


Questions

Will the updated requirements make it easier for you to submit themes?

-If no, what is making it difficult for you to submit themes?

Will the updated requirements make it easier for you to review submitted themes?

-If no, what is making it difficult for you to review themes?

Are there requirements that need to be removed, and why?

Is there anything in the list of requirements that is unclear? Describe the issue.

Can the formatting of the page be improved to make it easier to read?


#themereview, #themes-team

Gutenberg + Themes: Week of July 26, 2021

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

As always, please weigh in on the tickets below — your feedback is crucial and appreciated. 

Issues / Discussions & PRs

  • Themes: Cover 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.: Text color #33723
  • Themes/GS: 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. Global Styles: font family CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. not output on the frontend #33681
  • Themes: Weird theme.json behavior: block specific typography settings #33436
  • Themes: custom vars not working in edit/sote #33300
  • Themes/GS: Standardizing required theme CSS Variables #33180
  • Themes: Request for theme support option to enable and disable “full height alignment” #32900
  • Themes: Enable customization of the “full height alignment” value in Gutenberg, possibly changing it to add a CSS class rather than inline CSS #32899
  • Themes: A theme.json from child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/. is not merged with the one in parent theme #33512
  • Themes: Query Pagination Next: Add an arrow attribute #33656
  • Themes/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.: theme.json properties can’t be overridden in 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. #33367
  • FSE: Template Part placeholder – Add title step to creation flow. #33703
  • FSE: Query Title: add Search and 404 page titles #33515
  • FSE: Add credit block #33475
  • GS: Duotone filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.: Allow theme.json to set default filters for blocks #33642
  • GS: Dimensions Panel: Add new progressive disclosure panel and update spacing supports #32392

Merged/Fixed/Announced

  • Themes: I18n: Fix broken 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. in WP_Theme_JSON_Resolver #33624
  • FSE: Query Pagination: Update the arrows on the Next and Prev pagination blocks #33626
  • GS: Global Styles: Avoid rendering duplicate elements stylesheet #33680

Overview Issues

  • Global Styles: Design Tools Overview #33447

General Resources:

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

#gutenberg-themes-roundup

X-post: Help shape the future of theme design

X-comment from +make.wordpress.org/test: Comment on Help shape the future of theme design

Themes Team Meeting Notes – July 27, 2021

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

This meeting was based on the agenda. You can check agendas here

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,

  • 576 tickets were opened
  • 588 tickets were closed:
  • 559 tickets were made live. 
  • 30 new Themes were made live.
  • 529 Theme updates were made live.
  • 0 more were approved but are waiting to be made live.
  • 29 tickets were not-approved.
  • 0 tickets were closed-newer-version-uploaded.
  • Number of reviewers: 4

2. Discussion meeting with theme authors

The themes team is going to do a zoom call with theme authors regarding requirement changes on 28th July 2021. The list of interested theme authors are already prepared. For this first meeting, the spots are full. We can still do more at a later date if needed. If any theme authors are interested, please comment in the post or DM @kafleg.

3. Open Floor

In this part, we discussed and share few things. There were no discussions regards to theme development at today’s meeting.

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

#meeting-notes, #themes-team

Themes Team Meeting Agenda for July 27, 2021

Channel: #themereview | Time: Tuesday, July 27 2021, 15:00 UTC

The themes team conducts a meeting on the second and fourth Tuesday of the month.
The meeting takes place in the #themereview channel on the WordPress 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/. and you need an account to participate.

Along with the fixed agendas, we have an open floor at the end where you can ask or share anything related to themes.

We encourage all members and anyone interested to attend.

Meeting agenda

  1. Weekly updates
  2. Discussion meeting with theme authors
  3. 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.

Also check,


Discussion meeting with theme authors

The themes team is going to do a zoom call with theme authors regarding requirement changes on 28th July 2021. The list of interested theme authors are already prepared. For this first meeting, the spots are full now. We can still do more at a later date if needed.


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, #themes-team, #trt

Gutenberg + Themes: Week of July 19, 2021

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

As always, 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.: Fix nested layout containers. #33501
  • FSE Blocks: Query Title field is empty for search and 404 pages. #33476
  • FSE Blocks: Add option to change the arrows in the Query Pagination 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.. #33474
  • FSE Blocks: Consider a “Credit” block. #33475
  • i18n: Add pattern block. #33217
  • Global Styles: Add new progressive disclosure panel and update spacing supports. #32392
  • 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.: Discuss better behavior when using a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/.. #33512
  • Theme.json: Add a setting to opt-out of block templates. #33500
  • Themes: improve the way custom units are handled. #33470
  • Themes: theme.json properties can’t be overridden in 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.. #33367

Merged/Fixed/Announced

  • FSE Blocks: Remove arrows on the query pagination block. #33626

Overview Issues

  • Global Styles: Design Tools Overview #33447

General Resources:

#gutenberg-themes-roundup