Giving FSE a More User Friendly Name

tl;dr: The terms “full site editing” and “full site editor” (also abbreviated as FSE) were developed to easily refer to a collection of features and now that those features are integrated into our daily WordPress experience, how can we best update the wording to be more user friendly?

Not sure the difference between 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/, full site editing, and other terms here? Check out this post for high level definitions.

What I know

Many years ago when we started referring to some of the work going into Gutenberg’s Customization phase (Phase 2) as “full site editing” it was meant to differentiate from the work that had come out of Phase 1. Phase 1’s work was focused on bringing blocks to posts and much of the page surrounding posts, but Phase 2 was meant to move those blocks to the rest of the site editing experience—hence “full site editing”.

There are some issues with the term “full site editing”, though.

  • It was already possible to edit every part of a WordPress site using code. The term “full site editing” differentiated between phases of a project, rather than a new capability in the CMS.
  • To us, “full site editing” implies the use of blocks, but for new users there’s no reason for them to expect anything else. The term isn’t descriptive of what makes it unique.

As we continue the move toward a full-featured, true WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. experience for WordPressers of all skill levels, we should have a way to refer to it that is immediately meaningful for new users of our software, while also being an easy to reference term for all of us building and supporting the software.

What I see 

There are a few existing conversations around renaming Full Site Editing (both from a UIUI User interface/UXUX User experience perspective as well as a development perspective). From what I have seen in my reading, there are two primary contexts from a big picture perspective: Users & Visitors of WordPress; Contributors & Extenders of WordPress. That leads me to think we have two primary use cases for terms as well.

  • Users & Visitors of WordPress: I’ve heard a lot of people outside of the WordPress ecosystem simply referring to this as “the WordPress editor”. That seems mostly applicable to folks building with WordPress, selling on WordPress, or otherwise not creating the CMS itself.
  • Contributors & Extenders of WordPress: I have primarily seen references to “the 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. editor” with the understanding that work toward Full Site Editing is a suite of tools from within the Block editor, a framework that originated in the Post Editor but is extending to all areas of WordPress like the Site Editor, hence most editing interfaces evolving into “the Block Editor”. This seems mostly applicable to folks working in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., on Themes/Plugins, and by extension, also Training, Design, and Documentation.

What other contexts do you think we need to be aware of as we look toward making this more user friendly?

What I need

As with any audacious journey, one of the things that will hinder our success is not knowing what stands in our way. I would love it if you’d share your thoughts on the following questions!

  1. We’ve referred to it this way for a long time. How can we tackle renaming this together?
  2. It’s in the codebase. How will we make sure people who aren’t regular contributors see this?
  3. And repeating the in-line question from above: What other contexts do you think we need to be aware of as we look toward how to refer to our collective work in the future?

#core-editor, #editor, #gutenberg

Editor chat agenda: 27 July 2022

Facilitator and notetaker: @andraganescu

This is the agenda for the weekly editor chat scheduled for Wednesday, July 27 2022, 04:00 PM GMT+2. This meeting is held in the #core-editor channel in the Making 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/..

General Announcements and Links.

Key project updates

Task Coordination.

Open Floor – extended edition.

If you cannot attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat summary: 20 July 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, July 20 2022, 04:00 PM GMT+2 in Slack. Moderated by @bph.

Announcements and Links

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/ 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 13.7 was released today. What’s new in Gutenberg 13.7? (20 July)

Open Call For Comments on redesign and content of WordPress Homepage and Download page. Please share your ideas, opinions etc. It’s not every day that the home page is being revamped! The last one was 2016!

New Labels on the Gutenberg Repo

  • [Type] Developer Documentation new name for the existing [Type] Documentation` – Is also use for categorizing PRs for the changelog. (edited) 
  • The changes were necessary as we now also have [Type] User Documentation. It is used after the release,  for user-facing changes in UIUI User interface and screens. This is used by the end user documentation team to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. their work, especially around new WordPress releases.
  • A new label Backport to Gutenberg RC as added by @priethor – to help developers surface PRs that need to be cherry-picked for the current release cycle (fixes merged between RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). and stable plugin release)

Key project updates

Task Coordination

@mamaduka

Open Floor

Announcements, questions, and discussions.

@mamaduka

“I wanted to mention this message from @gziolo and PR from @Tenaki

“PR (42368) which brings consistency to the script names used in the Gutenberg project. We would appreciate feedback from other contributors to make sure it’s a move in the right direction.”

PR is ready to merge, but we’re looking for more feedback.

@poena

“Is there any support for re-adding the link color theme support for classic themes? How can I highlight this issue?  Consider re-adding link color support for classic themes
The background is that there is a ticketticket Created for both bug reports and feature development on the bug tracker. opened on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. about the text color option not working for links, and this seems to be because the theme support was removed rather than stabilized.”
I’m trying to understand if there is a way to re-enable the link color support that was available for classic themes in previous WordPress versions. I cannot even tell if the removal of the link color option was intentional.

@joyously

I had a concern about older issues in the GB repo. It seems the older ones are closed in favor of newer ones, but that loses the conversation and notifications of the older issue.

A recent example was about the Featured Image description.

The older issue was about the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 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. that went away, and it was being closed in favor of a newer issue about the description handled in JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors..

Nick Diego from the Triage Team noted: “Older issues that are the same should take precedence. Newer issues should be closed as duplicates, but some times, this doesn’t happen, often unintentional.”

@ndiego

I want to spotlight this PR in case anyone has feedback on it: Fix custom placeholder not displaying on subsequent Paragraph blocks. It seems minor, but impacts the creation of patterns with placeholder content, which are very useful in Agency/Client settings. Not exactly an adoption blockerblocker A bug which is so severe that it blocks a release., but would be very nice to fix.

To get more details go directly to the Open Floor discussions in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor 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.

Props to @paaljoachim for review

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Core Editor Improvement: Deeper customization with more template options

These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects.

With the last few releases of WordPress expanding what’s possible to edit on your site, from templates to theme blocks, Gutenberg 13.7 continues this work with more templates that theme authors and end-users can create directly from the site editor. If you’ve ever wanted to have a customized experience of a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. of posts, like your recipes or latest book reviews, or to have a unique template for a special post, you’ll enjoy what’s now possible. Here are the following templates that the last few 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/ releases have unlocked for editing directly:

  • Page templates: page-specific templates.
  • Post templates: custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. and post-specific templates.
  • Custom templates: user-selectable custom templates for all post types.
  • Taxonomy templates can be specific to a taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. (e.g., category, tag) or to a specific term within a taxonomy (e.g., category-slug).

Keep in mind that WordPress has supported these types of 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. templates since version 5.8 if developers manually bundled them in their themes. However, these changes allow users and extenders to create them directly from the new site editor interface. It also brings us one step closer to building more complex WordPress themes without writing code.

There are tons of use cases for these types of templates, only limited by what their creators want to build. For example, a user might want to show a grid of posts for a specific “photography” category but not change the default list style for others. A restaurant owner might remove the site’s default 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. on the “menu” page to let photos of the dishes take center stage.

To ensure third-party plugins can properly take advantage of this system too, work was done to clarify taxonomy-specific templates labels. Specifically, some custom taxonomies from third-party plugins share the same label (e.g., post categories and product categories both using the “Categories” term). In 13.7, the taxonomy slug is added in parentheses for additional clarity.

Custom Template Examples

To add custom post type or taxonomy templates, visit Appearance > Editor in the WordPress adminadmin (and super admin). Clicking the WordPress icon/button in the corner of the screen will open the sidebar panel. From there, select the Templates option.

At the top of the new page, click the “Add New” button to open the template dropdown as shown in the following screenshot:

WordPress admin screen that displays a list of the current templates.  The "Add New" dropdown button is selected in the top right with a list of new templates to create.

There should be several options listed with a default WordPress install with customization options:

  • Page
  • Category
  • Tag
  • Single item: Post
  • Custom template

Creating a Custom Page Template

To create a custom page template, select the “Page” option from the Templates > Add New button’s dropdown menu. A new overlay will appear on the screen for selecting a specific page to apply the template to, as shown in the following screenshot:

Overlay popup for selecting a page to create a template for, showing a list of pages.

The overlay lists the site’s pages and a search field for quickly looking up a specific page. Creating a new template is a matter of selecting the page. WordPress then redirects to the editor for building out the template’s block content.

The Page, Post, and Custom template options are all similar in scope. However, there are some slight differences:

  • Page allows creating individual templates that can be applied to a specific page on the site or as the default page template (if not already defined by the theme).
  • Single item: Post allows users to create post-specific templates or the default template for all posts.
  • Custom template is for creating a custom template that can be assigned to any post, page, or custom post type.

All three types of templates essentially allow you to define a custom template for a post. The primary difference is that “page” and “single item: post” are assigned automatically to their respective page or post. However, the “custom template” is not assigned to until a post/page author selects it from the template dropdown on the post-editing screen.

These templates are often used to change the outer layout instead of the content for a specific post. For example, you could create a “custom template” that uses a Cover block for a featured-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. area. Then, assign it to posts or pages when you want a large banner image to stretch across the screen, as shown in the following screenshot:

WordPress site editor with a cover image behind the site header and post title. The "use featured image" option is selected for the cover block.

There are no limits on how to design a template’s layout. Another common situation is adding or removing a sidebar for specific pages, depending on what the theme’s default is.

Creating a Custom Category Template

To create a new category template, select the “Category” option from the Templates > Add New button’s dropdown menu. The overlay will offer two choices, as shown in the following screenshot:

Overlay popup that displays two options:  one for a default category template and one for a specific category.

The first option is for creating the default category template. This is used as a fallback when a more specific category template does not exist. Selecting this option will immediately create the template and move you to the editor for customization.

The second option is for creating a custom template for an individual category. For example, perhaps you write posts about each WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. you attend and want to have a specific template that adds some additional context when folks look at all of your WordCamp posts. Selecting this option opens a new set of choices for selecting the category, as shown in the following screenshot:

Overlay popup that displays a category selection list.

Like creating a page-specific template earlier, the process is the same. Select the category and edit the new template from the site editor.

Tag and custom taxonomy templates work the same as above for ease of use.

A Look at What’s Next

Expanding what templates can be added continues on with only a few additional use cases to cover. Beyond that overarching work, there are a few open tickets related to custom templates that folks can follow if they are keen to see how this experience will continue to improve. One such ticketticket Created for both bug reports and feature development on the bug tracker. discusses pre-populating new templates from a fallback template within the template hierarchy. This means you would be presented with content already in the template rather than starting from scratch, greatly saving time.

Another PR focuses on improving the experience of clearing customizations when a user has customized a theme’s template. Currently, the description reads “Restore template to default state” whereas the update would offer clarification by changing it to “Use the template as supplied by the theme.”

Taken together all of these should help users and extenders alike embrace these new ways to customize your site.

Notes

The Custom template option cannot currently be assigned to specific post types. Templates created via this option are available for all posts, regardless of type. For example, the UIUI User interface does not account for creating a template that users can assign to only pages and/or products (custom post type). This is supported via the template hierarchy, and theme authors can still manually create them.

Custom templates are also not defined in the theme.json when exporting the theme ZIP file via the site editor.

Props to @annezazu for co-writing, proofreading, and outlining the scope for this post.

#core-editor, #core-editor-improvement, #gutenberg

Editor Chat Agenda: 20 July 2022

Facilitator and notetaker: @bph

This is the agenda for the weekly editor chat scheduled for Wednesday, July 20 2022, 04:00 PM GMT+2. This meeting is held in the #core-editor channel in the Making 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/..

General Announcements and Links.

  • Notes from last week’s meeting: Editor chat summary: 13 July, 2022
  • Open Call For Comments on redesign and content of WordPress Homepage and Download page
  • Gutenberg 13.7 RC-2 is available for testing – final release in the afternoon
  • New and changed labels in GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ Repo:
    • [Type] User Documentation
    • [Type] Developer Documentation and
    • Backport to Gutenberg RC

Key project updates

Task Coordination.

Open Floor – extended edition.

If you cannot attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

Post reviewed by @paaljoachim. Thank you.

#agenda, #core-editor, #core-editor-agenda, #meeting

Editor chat summary: 13 July, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, July 13 2022, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

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/ 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 releases

Gutenberg 13.7 RC1 was released 13 July.
It was quite a bit release with 154 PRs. Great work everyone!
A big thank you to @bph for handling this release!

Key project updates

Task Coordination

@mamaduka

@wildworks

@paulopmt1

I’m worked on a PR for added WhatsApp icon to the Social Icon Block

Open Floor

Announcements, questions and discussions.

@mrwweb

I can’t attend the meeting due to timing, but I want to call attention to #40381 which continually gives me headaches.
It appears that a “Classic”/hybrid theme using theme.json can only define the blockGap style if it also supports the blockGap setting. This doesn’t make any sense, because without the style, the editor displays all blocks with no gaps at all when theme.json is present.
It seems that simply always defining –wp–style–block-gap when there is a value present in theme.json would be a pretty easy way to resolve most of this issue.
Thanks!
(Needs feedback.)

@ndiego

I wanted to quickly spotlight a few issues from our Editor Weekly Bug Scrubs. Both have seemly valid PRs and need more testing and review. Both are a bit beyond my expertise level, and would love an extra set of eyes. If anyone has some spare time, it would be greatly appreciated.
No visual feedback when Parent Page dropdown is loading.
The block editor does not trigger the interim login modal early enough
(Needs feedback.)

@fabiankaegy

I just wanted to raise this issue that @bph created: 
GitHub Action for ‘docs:build’ step after documentation changes.
I’ve seen the required build step of the docs add quite a bit of friction to many first time contributors and even experienced folks trying to help with documentation recently and think it would be great if we could come up with a way to make that step happen in CI.
(Needs feedback.)

To get more details go directly to the Open Floor discussions in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor 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.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat summary: Wednesday, 06 July 2022

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor 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, on Wednesday, July 06, 2022, 14:00 UTC.

General Updates

Async key project updates

Read the latest updates directly from the following tracking issues:

@jorgefilipecosta

  • On the styles and style engine projects created a PR ready that outputs the presets specific to a section. It is ready for reviewWith it a group 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. e.g: used in a pattern can have its own presets e.g: its own color palette its own gradients etc 
  • A PR with an identical mechanism for descendent block styles is also available at.
  • On the site editor and templates project, I created a PR that allow the user to create a generic template from the site editor and another that allows creating templates for specific authors.
  • On the building with patterns project, I have a PR ready that allows one to limit the usage of its pattern to specific post types.

Task Coordination

@zieladam

  • Focusing on merging the editor changes to WordPress 6.0.1 and also exploring add a .wp-block-heading CSS class to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./heading block – and perhaps other blocks as well?
  • Published another part of the WordPress data tutorial

@jorgefilipecosta

  • Worked on adding new templates to the UIUI User interface, outputting presets at the block level and descendent block styles, and the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. that allows restricting patterns to specific post types.
  • Next week I plan to continue expanding the template creation with the UI supports, iterate and merge the current PR’s .
  • Pick a new task if we manage to finish the expansion of supported templates on the UI.

@fabiankaegy

  • I’d love to get a pair of eyes on this PR that a college prepared. It adds a setting to theme.json to allow developers to control whether the width control of the Core Buttons block gets shown to the user or not 

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Read complete transcript

#meeting-notes, #core-editor, #editor, #gutenberg, #core-editor-summary

Editor Chat Agenda: 13 July 2022

Facilitator and notetaker: @paaljoachim

This is the agenda for the weekly editor chat scheduled for Wednesday, July 13 2022, 04:00 PM GMT+1. This meeting is held in the #core-editor channel in the Making 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/..

Gutenberg 13.7 RC

Key project updates:

Task Coordination.

Open Floor – extended edition.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

Editor chat summary: Wednesday, 29 June 2022

This post summarizes the weekly editor chat meeting on Wednesday, 29 June 2022, 14:00 UTC held in Slack.

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/ 13.6 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).

@jorgefilipecosta Released Gutenberg 13.6 RC today. The release could be downloaded at https://github.com/WordPress/gutenberg/releases/tag/v13.6.0-rc.1. The changelog could also be checked on the same link.

WordPress 6.0.X

Information related to future patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. releases of 6.0 can be checked on https://make.wordpress.org/core/2022/06/25/wordpress-6-0-x-release-team-and-6-0-1-schedule/.

On the editor side @zieladam is going to help with 6.0.1 for future releases there is an opening if someone is able to help.

WordPress 6.1

The planning post for WordPress 6.1 is available at https://make.wordpress.org/core/2022/06/23/wordpress-6-1-planning-roundup/. There are some positions opened on the release squad so if something interests feel free to volunteer in that post.

The BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 & Feature Freeze is scheduled for September 20, 2022.

Key project updates

Building with patterns & Styles

Now we have the ability to use start patterns on a modal on other post types besides pages https://github.com/WordPress/gutenberg/pull/41791. A much-requested feature.

@jorgefilipecosta proposed PR to target descend 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. styles in a block using s shape equivalent o 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. on https://github.com/WordPress/gutenberg/pull/41922. It allows more styling flexibility when building a pattern.

Task coordination

@get_dave

@jorgefilipecosta

  • Previously:
    • Proposed a mechanism to allow the usage of the start post pattern modal on other post types besides pages.
    • Added an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to allow a pattern to be restricted to some post types
    • Proposed an API to allow blocks to style their descendent blocks.
    • Multiple bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes, code enhancements, and reviews.
  • Future:
    • Implement the rendering of block-level presets.
    • Help the effort to expand the templates that can be created on the site editor.

@mamaduka

Is looking for technical feedback/review for my new PR to allow locking inner blocks from the container block – https://github.com/WordPress/gutenberg/pull/41876.

Open Floor

Toolbar regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.

@get_dave said that the toolbar has suffered a regression whereby it now obstructs blocks that are at the top of the viewport. The Nav block is badly affected by this. If anyone is available to work on this that would be great. I know @talldanwp has also promised to give it some attention.

@jorgefilipecosta asked if already know the PR that caused the regression. @get_dave said the popover component upgrade is the probable cause and added @talldanwp is investigating.

Weekly bug scrub

@NickDiego shared in the meeting that now we are now holding weekly Editor Bug Scrubs at 1400 UTC on Tuesdays here in #core-editor he and @mamaduka held the first one this week. Everyone is encouraged to participate and help on the weekly bug scrubs.

Request for RTL testing

@poena said:

There is a PR for RTL styles that could use more testing by someone who uses an RTL language as their default for the editor:

https://github.com/WordPress/gutenberg/pull/41762

So if you usually use RTL language your help is greatly appreciated.

#agenda, #core-editor, #editor, #summary

Making the Tech Editor Release Lead Role More Creative and Less Repetitive

Merging 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/ to WordPress on major releases is now more automated than ever.

@zieladam (me) and @gziolo were the tech editor release leads for WordPress 6.0. We’ve quickly noticed that ~30% of the role is about communication and decision making, while ~70% consists of repetitive weekly chores. We want to reverse these proportions.

Most repetitive work falls into one of the two categories:

  • Backporting PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes made in 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 since the previous major WordPress release
  • Releasing weekly BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). versions

Backporting PHP changes made in the Gutenberg plugin since the previous major WordPress release

Finding and backporting all the PHP Pull Requests merged to Gutenberg but not to WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is a huge task.

For WordPress 6.0, it took us two days just to prepare the list. From there, it was two weeks of pinging, coordinating, reviewing, and merging code before we were done. Furthermore, not all the authors had the availability to help at that point in time.

This cannot be easily automated, but imagine the alternative: Gutenberg developers prepare PRs against WordPress core in parallel with merging their Gutenberg PRs. Any integration issues get surfaced right away, there are fewer merge conflicts, and the release leads don’t have to spend two weeks investigating the commit history and pinging code authors. The future availability of the developers isn’t a problem anymore either.

If that sounds appealing, come and speak up in the ongoing GitHub discussion!

Releasing weekly Beta/RC versions

The weekly release consists of four repetitive tasks:

  • Cherry-pick triaged code to a Gutenberg release branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".
  • Release Gutenberg @wordpress packages from that branch
  • Update the version of packages used in wordpress-develop
  • Manually stabilize any blocks to be included in the new release

@zieladam (me) and @gziolo added a degree of automation to all of the above.

Cherry-pick triaged code to a Gutenberg release branch

Bringing Gutenberg Pull Requests over to WordPress after Beta 1 requires cherry-picking the relevant commits.

Before, this involved manually resolving conflicts and letting the author know. A few times I got confused and spent more time on it than I hoped to.

Today, the new npm run cherry-pick script automates all of that (except resolving conflicts). Furthermore, it can be repurposed for the Gutenberg plugin releases.

Publish the updated @wordpress packages from the release branch

After cherry-picking the relevant changes to the release branch, the way to bring these changes to WordPress core is through npm packages.

Before, it took publishing permissions, a specific local setup, and remembering the correct command with the proper CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. parameters. With all that in place, you ran the built process, waited a longer while, and then published the packages.

Today, this entire process can now be triggered directly from GitHub UI after approval from any Gutenberg core team member.

Update the version of packages used in wordpress-develop

With fresh @wordpress packages published to the NPM registry, the next step is to update the dependencies in wordpress-develop.

Before, it involved a manual synchronization of the new Gutenberg dependencies with the package.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 shipped in wordpress-develop. You had to add any new dependencies, update the versions of the existing ones, and delete ones that were no longer used.

Today, the new sync-gutenberg-packages console task automates this effort.

Manually stabilize any blocks to be included in the new release

Finally, a number of steps are required to enable the new stable blocks in WordPress core.

Before, you had to manually list the new blocks in a few .php and .js files and double- or triple-check whether all these lists are in sync. As there are other build steps at play, the resulting Pull Request is quite large. Even though @zieladam and @gziolo were careful, we still ended up making mistakes.

Today, the new sync-stable-blocks console task reduces the entire process to running a single command. All the relevant lists are generated automatically making the process easier and removing any chance for human error.

Next steps

Wiring the above automations to run sequentially would streamline the entire process to a single click of the button:

  • Take a list of Gutenberg PRs as an input
  • Create a Pull Request against wordpress-develop as an output (example)

With the caveat that merge conflicts would still have to be resolved manually.

I’d love to inspire the next release squad to explore this during the 6.1 release cycle.

By simplifying these two large areas, I believe we can truly make the Tech Editor Release LeadRelease Lead The community member ultimately responsible for the Release. role mostly about the decision, communication, and creative work without so many repetitive tasks.

Props to Héctor Prieto (@priethor) and Grzegorz Ziółkowski (@gziolo) for their help in putting this post together.

#6-0-1, #6-1, #core, #core-editor, #gutenberg