Andrei Draganescu 8:34 pm on September 8, 2021
Tags: core-editor ( 703 ), core-editor-summary ( 185 ), summary ( 817 ), themereview

Editor chat summary: 8 September, 2021

This post summarizes the weekly editor chat meeting (agenda here) held in Slack. Moderated by @andraganescu.

Announcements

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/ 11.5 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). launched today (Sep 8)

@mikeschroder released Gutenberg 11.5 RC. You can take it for a spin from here.

Important resources for the incoming period of time

@priethor added some details about where we should look for guidance around the incoming updates to WordPress in light of the 5.9 release:

There will be an upcoming What’s Next in Gutenberg post based on the preliminary road. It’s worth noting the “What’s Next” intent is to highlight issues where contributors can help, whereas the high-level plan is defined in the preliminary road post.

Key Project Updates

Navigation Editor

@get_dave shared this week’s update:

Everyone is focused on addressing the High priority issues on the Tracking Issue.
Work has continued on the Submenu block and preparing it ready for use in the Nav Editor.
The navigation editor 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. has gained more tools to better match other editors – props to @talldan for all his work here.
Work is underway to add a global inserter to the screen.
The creation flow for navigation menus was improved with a new block placeholder
Improvements to List View drag and drop should have beneficial knock-on effects for the Nav Editor – props to @gwwar for her work here.
We could do with the ability to (multi) select non-consecutive blocks. This PR from @swissspidy looks promising but additional help much appreciated.

Mobile

From mobile, @hypest offered the updates:

Shipped

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. picker search.
Inline previews for YouTube and Twitter embeds.
Alignment options for embeds.
New experimental Gallery block.

In Progress

Embed block.
GSS Font size, line height, colors.

Components

@mciampini shared some updates from the folks working on the components package:

Shipping:

The PolymorphicComponent types have been renamed to WordPressComponent
A new color picker component and adapter for the old API have been added to support the new Global Styles design.

Notable fixes:

Some Storybook improvements and fixes for the recently added ToggleGroupControl component.

In Progress:

Some further refinements to the new color picker design.
Updated components contributor guidelines.
Iterating on some interactions in the new ToolsPanel component and porting it to TypeScript. This component will be used extensively in the new Global Styles 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..

Task Coordination

Feel free to add items to this post if you weren’t able to make the meeting.

@ntsekouras

Social Links use the new flex layout
Add layout default value support for blocks
Add arrow and syncing of it for Query Pagination block for Next and Previous blocks

@joen

Doing lots of nav block reviews, excited to see the cool stuff coming. Otherwise, I’m in mockup country with duotone, color swatches, generic inspector panels, alignments and other things.

@mamaduka

Updated documentation to replace withSelect HOC references with useSelect.
Worked with Riad to fix code data issue with include query parameter.
Checked on approved PRs, merged some, and left comments on others to see if authors have time to address the feedback. (Sorry if you received more notifications than usual)

I would appreciate feedback on the following PRs:

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. Fetch: Improve isMediaUploadRequest check
FSE: Add basic support for child themes

@get_dave

I’ve been AFK but back now and re-focusing on all High issues in the Nav Editor Tracking Issue.

@jorgefilipecosta

During the last week I updated the design of the mosaic view, I iterated on the engine to allow blocks to be aware of global styles, I proposed the PR to enhance the design of the new color picker and I did multiple PR reviews. I also started the effort to replace tinycolor with colord.
For the next week I place on continuing the color library replacement, Iterate on the color picker design and pick another task related to the global styles new design.

@zieladam

I paired up with @jsnajd to migrate core-data from redux-rungen to thunks and async/await.

@annezazu

Shipped the theme switching exploration for the #fse-outreach-experiment, shipped the last FSE testing call summary for handling highered headers, should be shipping the next coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor improvement post later today, and have done a fair bit of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.! I’m also going to run a hallway hangout in #fse-outreach-experiment on this Friday at 1:30 PM UTC covering some of the latest and greatest FSE related issues

@mciampini I plan on:

making progress on the @wordpress/components contributing guidelines
reviewing and giving feedback on PRs affecting components (e.g @jorgefilipecosta ’s work on color picker, or the ToolsPanel refinements)
creating more tracking issues (like this one on Typography tools) to highlight the next steps towards implementing the new Global Styles sidebar

@oandregal

I’ve been working on enabling the global stylesheet for all themes and other minor improvements. Prepared a PR to make sure themes with 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. load the styles fine in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. as well as the theme directory.
In the area of alignments: landed a PR that makes the wide control only available if the theme provides a wide size and prepared another for fixing floats (left, center, right) for blocks that are not part of a container.

Open Floor

Will PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher minimum required version change in WordPress 5.9?

@anil (Anil Sardemann) asked about the future min. PHP requirements of 5.9. @hellofromtonya explained that there are no plans to change the minimum supported PHP version in WordPress 5.9 since still more than 5% of WordPress runs on PHP 5.6.

Help with the future of Block Theme Switching

@annezazu brought more attention to the FSE Program Exploration: Help with the future of Block Theme Switching. This is a very new approach in that it’s all about gathering insights to help shape the potential designs rather than testing a specific flow. It’s neat to be able to be involved this early in solving a problem. Check it out, share your thoughts, and get creative!

Help needed with review

@faizan asked for a review on his 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. on Ticket 50074

#core-editor, #core-editor-summary, #summary, #themereview

annezazu 2:50 am on September 2, 2021
Tags: core-editor ( 703 ), core-editor-summary ( 185 ), summary ( 817 ), themereview

Editor chat summary: 1 September, 2021

This post summarizes the weekly editor chat meeting (agenda here) held in Slack. Moderated by @annezazu.

Announcements

Release notes coming soon after a quick fix. For now, some highlights:

The Gallery 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. now acts as a wrapper for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Image Blocks thanks to the Gallery Block Refactor. 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 and theme authors, please do check out out this dev note to get up to speed on backwards compatibility
The Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. block now has the option to add duotone filters so you now have even more ways to add your own style to your content.
Padding support was added to the Buttons Block making it easier to get the spacing just right.

5.8.1 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). launches today (Sept 1)

Based on the schedule previously shared, 5.8.1 RC will launch today with the release coming on September 8th. If you can, please help test the release.

Final day for the current FSE call for testing (Sept 1 )

It’s the last day to explore the current FSE Outreach Program call for testing. If you have time, share your thoughts! If you don’t, please help amplify by sharing with others.

Reminder: monthly block theme meeting in #themereview

A reminder was shared that there is a block theme meeting in for anyone keen to chat about what’s happening with block themes. This is a recurring monthly meeting so if you missed today’s, don’t worry!

Monthly Priorities & Key Project Updates

The overarching plan for September has not yet been shipped yet so we based today’s conversation on the July & August Plan. As a reminder to those working on these projects, async updates are both welcomed if you can’t make the meeting and needed.

Navigation Editor

For the Navigation Editor portion, @talldanwp shared a lovely update. Here are some highlights:

A plan has been formed for migrating from the customize 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 the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. in the navigation editor.
The nav editor 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.’s design has been refreshed.
Some conversation is underway around extensibility of the editor (join in if you’re interested).

Mobile

Shipping:

Block picker search

Notable fixes:

Fixed an npm install breakage on Gutenberg’s trunk 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". due to third-party dependency we were building that had an unpinned typescript dependency.

In Progress:

Embed block (hoping to release some inline previews in our next release)
GSS Font size, line height, colors

Patterns

For patterns, some context was shared amongst the core editor wranglers from @paaljoachim that the design tool overview enhancements will ultimately also trickle down to make pattern creation easier, more responsive, etc.

Styling

I’m going to reuse part of the async update from André since he’s done a ton of work there. Lots of work is underway with adding duotone support in theme.json along with a PR around enabling global styles to all themes. Expect work to continue on this path for the week ahead.

No update for the Template Editor or the Navigation Block

If anyone has any context to add around the Template Editor or the Navigation Block, feel free to chime in below in the comments.

Task Coordination

Feel free to add items to this post if you weren’t able to make the meeting.

@mikeschroder

Shipped:

Closed 32024 via [51677]. Thanks everyone for your help, including with the follow-up tests commit!
Opened two Video Block poster related PRs (34415 and 34411).

This week, planning to investigate 33437.

@oandregal

Recently updated GitHub username.
Helping with reviews, most notably adding duotone support in theme.json.
Created a few PRs in this area of work: the main one is perhaps enabling global styles to all themes. I’ll continue to work in this area for the next week.

@zieladam

Merged a new widgets /render endpoint
Started “thunk-ifying” of core-data, got to the point where we’re able to slice Jarda’s main PR into a series of smaller, high-velocity PRs. The first one was #33201 and more are coming
Fixed a few problems with retrieve_widgets in core a bit (1524, 1525)
Brainstormed the navigation /reorder endpoint in #25093
Started #34335 to fix sending too many API requests when saving widgets. It seemed simple at the beginning but we ended up asking “should we support .raw attributes and other post-specific logic in core-data?”

@youknowriad

I’ve worked a bit on performance. I want to get back to some layout related work.
I’ve reviewed a number of PRs as well.
I’ve spent some time this week exploring some wild ideas for block registration (both to make easier and more universal/language independent). For the curious, the repo is here https://github.com/youknowriad/blocky it’s no where near ready but I’d love to learn more about your custom blocks, if you have examples or ideas about how you’d ideally write them and what use-cases would you want to see for the simplified “view” property.

@joen

I’m as always focused on the navigation block and all sorts of things related to that, lately with some mockups for how to enable click-invoked dropdown menus, as well as refactoring to use gap for spacing menu items.
A lighter navigation building experience remains a priority, and I’d love to pair with a developer on exploring the approach mocked up here.

@gziolo

I worked on a proposal to split block registration from filtering, but I landed on a solution that ensures that all 3rd party filters are correctly (re)applied to all registered blocks. It might fix many existing issues for 3rd party blocks and their integration with plugins that extend blocks. It waits for feedback.
I’m still waiting for feedback for the proposal that adds a way to absorb inspector controls from the parent block.

@annezazu

Recapping and responding to the current call for testing for the outreach program.
Finalizing the next call for testing(more exploration than call for testing right now on theme switching).
Drafting some core editor improvement posts + assisting with an upcoming News post
Shipped a YouTube video all about patterns.
Triaging unlabeled PRs (down from over 100 to in the 20s). The unlabeled PRs that are left I am not quite sure what to do with so feel free to jump in.

Open Floor

Offer to run a Gutenberg Release for the first time. Raised by @mikeschroder.

If folks are interested, after shadowing @talldanwp (thanks again!), I would love to try running a Gutenberg release for the first time. Whenever it works best for the team is okay with me!

Next step: @priethor will coordinate since he helps wrangle the release process.

Proposed migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of E2E specs to Playwright. Raised by Bart Kalisz.

A proof concept was shared and well received thus far as part of a proposed migration to Playwright. At this point, a wider discussion needs to happen with impacted parties to ensure that folks are willing to follow the proposed changes. A few folks chimed in agreeing that a wider discussion needs to happen along with perhaps a comparison with Cypress (mentioned by @swissspidy). Depending on how things go, a Make Core post might make sense.

Next steps: Bart alerted the crew in #core-test and @annezazu will ensure that it gets discussed in the Core Dev meeting for wider attention.

Call for community ideas for FSE Outreach testing calls. Raised by @annezazu.

I’d love to start experimenting with community members sharing ideas for what to test in the outreach program. If you’d like to suggest an idea for a call for testing, know it’s very welcomed and all ideas will be weighed against current project priorities to figure out what makes the most sense to pursue. You can share ideas directly in the #fse-outreach-experiment 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 or via DM to me! In case you’re curious about how calls for testing have been wrangled in the past, it’s typically been a combination of monthly project priorities/release priorities + my own testing/what I can make happen + conversations with contributors.

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

annezazu 7:43 pm on February 1, 2021
Tags: core-editor ( 703 ), feature-widgets-block-editor ( 8 ), gutenberg ( 473 ), gutenberg-next ( 23 ), themereview

What’s next in Gutenberg? (February 2021)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for February. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development-related posts and a Site Editing Milestone overview issue that breaks down the upcoming work into more concrete next steps.

Preparations for WordPress 5.7

This release will include versions 9.3 to 9.9 of Gutenberg! The WordPress 5.7 Must Haves project board includes issues that need attention in preparation for the WordPress 5.7 release. Many contributors will be spending the month of February working on bugs and regressions to be fixed for inclusion in WordPress 5.7. As a reminder from this originally planning post, these are the main focuses:

Update WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to include current releases of 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.
Gutenberg: ship additional blocks, refine the UIUI User interface, add tools for themes and design, and continue working on the 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. screen.
Continue work on auto-updates and jQuery.

Finally, a number of issues have been gathered in this issue for Dev Notes (more information on these notes here). Dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are typically published along with the first Release Candidate which is currently scheduled for February 23rd, 2021.

Global Styles

Review this overview issue to see what’s planned for the V1 in 5.7.
Explore this issue to see the latest plans for improving the UI.
Join the discussion around how best to handle various styling use cases.
At a high level, you can find the latest update for the project overall here.

Of note, the parts of Global Styles that will land in 5.7 will solely concern 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. structure and won’t impact users.

Follow along:

You can follow the progress for this overall system in this overview issue and by reviewing the Global Styles label.

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 Widget Editor

Work on the Block-based widget editor (Widgets Screen) is a continued focus for the month ahead. The purpose of this effort is to bring the flexibility of block-based editing to the widgets and customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. screens. You can find more information about the current work in progress in this exploratory issue for bringing blocks to the customizer and this summary issue for overall items for a block based widget editor experience.

Follow along:

You can follow the progress of this work on this project board and you can join #feature-widgets-block-editor in 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/ 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/. for future widget screen focused meetings.

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue as a big picture goal for 2021. Work this month will include the following focus areas:

Milestone 1 – Site Editing Infrastructure and UI

Iterate on Template editing mode including integrating feedback from the first round of FSE testing.
Introduce semantic templates parts and distinguish them in the block tree including aspects like adding a “section” term.
Exploring a design for how best to restrict block editing capabilities based on editing context.

Milestone 5 – Query Block

Query Block toolbar controls revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. to make it easier to show the content you want.
Exploring the idea of a Query Block builder UI to scale the experience for advanced users.

Milestone 6 – Navigation Block

Work on the Navigation Block is an ongoing effort and focus for February. An overview of the work in progress can be found in the Navigation Block tracking issue.

We’re still watching the Theme Experiments repo to see how theme developers are building block-based themes. Please continue to share there and know we appreciate it.

Follow along:

You can follow the progress of this project with this overview issue showing key milestones for site editing. For each major milestone, there are related issues you can follow if you want a more granular look at each next step (example from Query Block).

As a reminder, if you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more.

Areas to be aware of:

Block & Plugin Developers

Thanks to collaboration between @jessplease and @gziolo (and others!), a new package was created in this PR to make it even easier for developers wanting to develop their own third-party templates for the create-block package. You can read more about this addition on the @wordpress/create-block-tutorial-template reference page.

Theme Developers

A PR landed over the last month to load content in iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. for the site editor experience. This should help get rid of any CSSCSS Cascading Style Sheets. bleeding and allow a theme stylesheet to be dropped in the editor without any necessary adjustments. For theme authors this is something to be aware of as it should make block theme authoring easier!

Finally, there’s a comprehensive overview issue covering updates to experimental-theme.json that’s worth digging into to stay up to date.

Navigation Screen Work

Navigation screen work will be continuing this month but is a lower priority currently than the other areas listed above. A design iteration is underway as part of this effort. You can follow this work here and you can expect it to be a higher priority in the months to come.

Ways to Get Involved:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues, and reviewing PRs. In particular, if you’re interested in helping with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. but don’t know where to start, there’s a new course on Learn WordPress for how to do triage in GitHub! Check it out and join us.

If there’s anything we can do to make contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

Core Editor weekly @ 14:00 UTC in #core-editor focused on all things Gutenberg.
Block-Based Themes meeting twice monthly at Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

#core-editor #gutenberg-next

#gutenberg

Daisy Olsen 12:46 am on January 7, 2021
Tags: core-editor ( 703 ), feature-widgets-block-editor ( 8 ), gutenberg-next ( 23 ), themereview

What’s next in Gutenberg? (January 2021)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for January. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Global Styles

Global Styles refers to the system that defines and manages global aesthetics, allowing overall site styles, theme styles, and blocks to work well together. Global Styles focus areas for January include:

Determining what 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. and infrastructure functionality (not user facing) to include in WP 5.7
Support for translation theme.json strings

Follow along:

You can follow the progress for this overall system in this overview issue and by reviewing the Global Styles label.

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 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. Editor

Blocks in the Widget Screen

Adding block support for the widget editor is an ongoing focus. Progress toward this effort can be accessed via the Block-based Widget Editor project board. The emphasis for January will be eliminating bugs.

Blocks in the Customizer

An exploratory phase to find the best path for adding blocks in the customizer. If this interests you, please review this previous discussion and check out the current plan for exploration. For greater context, you can also watch this hallway hangout focused on managing blocks in the customizer.

Follow along:

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue iterating over the coming months. Work this month will include the following focus areas:

Milestone 1 – Site Editing Infrastructure and UI

Work toward infrastructure and UIUI User interface improvements including:

Milestone 5 – Query Block

This work includes the following Query Block design explorations:

A pagination block with different style variations to work alongside the Query Block.
Query Block toolbar controls revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. to make it easier to show the content you want.
Exploring the idea of a Query Block builder UI to scale the experience for advanced users.

Milestone 6 – Navigation Block

Work on the Navigation Block is an ongoing effort and focus for January. An overview of the work in progress can be found in the Navigation Block tracking issue.

In addition to the above, the Theme Experiments repo is being monitored to see how theme developers are building block-based themes. Please continue to share there, it is appreciated!

Follow along:

As a reminder, if you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more.

Important Note:

If you were previously following this project board, it has now been closed in order to use the milestones issues more consistently and to prevent people from needing to follow the progress in two places.

Areas to be aware of:

Block & 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 Developers

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 has been released please review the Dev Notes in the 5.6 Field Guide with a particular focus on preparing your plugins for PHP 8.

Theme Developers

Those interested in learning more about block-based themes may wish to read the comprehensive article @frankklein wrote on what he learned while building a block-based theme.

Ways to Get Involved:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues, and reviewing PRs. In particular, for this month, focusing efforts around testing the Widgets Screen would be very helpful and high impact.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor weekly @ 14:00 UTC on Wednesday in #core-editor focused on all things Gutenberg.
Block-Based Themes meeting twice monthly Wednesday @ 16:00 UTC on Wednesday in #themereview focusing on preparing for Full Site Editing enabled theme development.
Block-Based Widget Editor meeting weekly @ 07:00 UTC in #feature-widgets-block-editor on Wednesday focusing on implementing the ability to manage blocks in widget areas.

#gutenberg-next

annezazu 8:08 pm on December 1, 2020
Tags: core-editor ( 703 ), feature-widgets-block-editor ( 8 ), gutenberg-next ( 23 ), themereview

What’s next in Gutenberg? (December)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for December. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Addressing WordPress 5.6 feedback

WordPress 5.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). 2 is set to ship on December 1st with the General Release following on December 8th. During the Release Candidaterelease 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). period development will be limited to addressing critical regressions and bugs. Ideally, this won’t be an area that needs great attention for this month’s work thanks to the great effort put in thus far to make this release a success.

Follow along:

In addition to following individual features and their progress, you can follow where things stand on this WordPress 5.6 Must Haves project board.

Global Styles

Global Styles refers to the system that defines and manages global aesthetics, allowing overall site styles, theme styles, and blocks to work well together. Currently, the focus remains on tightening up and fixing the flows, with the goal of preparing a V1 that can land as a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. early in the 5.7 cycle. You can find an initial list of items for a V1 here that includes everything from exploring versioning for 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. to ensuring theme.json works cross-platform (web & mobile).

Follow along:

You can follow the progress for this overall system in this overview issue and by reviewing the Global Styles label.

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. Screen

After pausing this work for November, the Widgets Screen is once more a focus for the month ahead. Currently, this work involves an exploratory phase to find the best path for adding blocks in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.. If this interests you, please review this previous discussion and check out the current plan for exploration. For greater context, you can also watch this hallway hangout focused on managing blocks in the customizer.

Follow along:

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue iterating over the coming months. Work this month will focus on finishing up Milestone 1 – Site Editing Infrastructure and UI and Milestone 5 – Query Block alongside the overall Global Styles work previously mentioned. This work includes the following 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. design explorations:

A pagination block with different style variations to work alongside the Query Block.
Query Block toolbar controls revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. to make it easier to show the content you want.
Exploring the idea of a Query Block builder UI to scale the experience for advanced users.

Outside of the above, we’re still watching the Theme Experiments repo to see how theme developers are building block-based themes. Please continue to share there and know we appreciate it!

Follow along:

As a reminder, if you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more.

Important Note:

Areas to be aware of:

Please review the Dev Notes in the 5.6 Field Guide with a particular focus on preparing your plugins for PHP 8.

Theme Developers

Read the comprehensive article @frankklein wrote on what he learned in building a block-based theme.

Help test out the Twenty Twenty-One Block based theme and give feedback/report bugs.

Ways to Get Involved:

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

Core Editor weekly @ 14:00 UTC in #core-editor focused on all things Gutenberg.
Block-Based Themes meeting twice monthly at Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

#core-editor #gutenberg-next

Daisy Olsen 10:23 pm on November 2, 2020
Tags: accessibility ( 55 ), core-editor ( 703 ), gutenberg-next ( 23 ), themereview

What’s next in Gutenberg? (November)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for November. Please join us in our efforts and let us know in the comments if anything is blocking you from contributing.

Ways to follow along with Gutenberg development:

Here’s an overview of ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development related posts and a Site Editing Milestone overview issue that breaks down the upcoming work into focus areas.

Preparations for WordPress 5.6

The WordPress 5.6 Must Haves project board includes issues that need attention in preparation for the WordPress 5.6 release. Many contributors will be spending the month of November working on bugs and regressions to be fixed for inclusion in WordPress 5.6.

A number of issues have been labeled for Dev Notes. A dev note is a blogblog (versus network, site) post, published when a technical change that developers may need to know about will be included in the next WordPress release. Dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are typically published along with the first Release Candidaterelease 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). which is currently scheduled for November 17, 2020.

Full Site Editing

Work on this major focus for phase 2 is an ongoing effort and is expected to continue iterating over the coming months. For November, priorities are being evaluated in order to identify next focus areas for Full Site Editing.

Overview

The Full Site Editing overview issue #20791 can help to identify the major components that will be included in this effort.
The Full Site Editing project board is another good place to watch for more detail about the current status of this overall effort.
Site editing Infrastructure and UIUI User interface continues to be addressed in overview issue #24818.
An effort the ensure that Template tags are accounted for in Full Site Editing is underway in issue #22724.

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.

The Query Block is an important focus area. This feature is being explored in the following issues:

An Overview issue aiming to identify and resolve any Missing Query block functionality can be followed in issue #24934.
Design work for the controls for the Query block is being explored in issue #25198.
The Pagination Block is a part of the overall Query Block effort with design being explored in issue #26557.

Global Styles

Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together.

An overview issue #20331 contains detailed information about Global Styles.
The Global Styles effort is being actively evaluated to identify next areas to focus on as well as areas to de-prioritize.
An effort will be made adjust for some things identified during testing with the blocks based version of the Twenty Twenty-One theme.

Ways to Get Involved

While the above items are our focuses, you can always help with triage, needs testing issues, good first issues and reviewing PRs.

Meetings to Join

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor weekly meeting on Wednesdays @ 14:00 UTC in #core-editor focused on all things Gutenberg.
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) weekly meeting on Fridays @ 16:00 UTC in #accessibility focused on wrangling accessibility related work across Core and the block based editor.
Block Based Themes meeting twice monthly on Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

Note: with daylight savings time related changes happening for many countries on different dates it may be helpful to double check on the times as some meetings may shift times to accommodate attendees preferences.

#gutenberg-next

annezazu 8:33 pm on October 1, 2020
Tags: core ( 560 ), core-editor ( 703 ), gutenberg-next ( 23 ), themereview

What’s next in Gutenberg? (October)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for October. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development related posts and a new Site Editing Milestone overview issue that breaks down the upcoming work into more concrete next steps.

5.6 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 Preparation

With October 20th marking the cut off for WordPress 5.6 Beta 1, there’s going to be a shift in approach this month to focus on what can or cannot be ready for 5.6 since, after the Beta 1, there’s not a way to merge additional features. As part of this preparation, a decision was made by the people working on the Navigation and the editor tech lead for 5.6 to exclude the Navigation Screen from 5.6. Outside of this decision, this focus mainly impacts projects like the Widgets Screen and various editor focused APIs as they will each need to reach a certain threshold in order to be included. Expect there to be lots of effort here to fine tune and make decisions in preparation for an exciting 5.6 release!

Delaying 9.2 Release:

As mentioned in the latest core editor meeting, since Beta 1 for WordPress 5.6 is due on October 20, it’s likely that the next Gutenberg release will be delayed by one week in order to match the dates and include as many features as possible. This means that Oct 19th will likely be the 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). for 9.2 and the stable release will be done on Oct 21 since the packages can be incorporated into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. before Beta 1.

Follow along:

Outside of following individual features and their progress, you can follow where things stand on this WordPress 5.6 Must Haves project board.

Global Styles & Editor focused APIs

Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. While great progress was made in September, the editor focused APIs are still in experimental status and a decision will need to be made about what can be included in 5.6. It’s anticipated that 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. APIs might not be ready for 5.6 but the block.json one might be instead. Outside of decisions around 5.6, some of this work in the month ahead will include the following:

Adding support for themes to control the editor in a global context, and in a per 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. context.
Expand the global styles 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. with new options and improve its UIUI User interface.
Expand the typography controls and allow users to pick a custom font family and font-weight, and allow themes to configure which font families are available.
Add functionality that allows users to use the global styles sidebar to control the editor’s behavior like which color palette is active.

Follow along:

You can follow the progress for this overall system in this overview issue. For more recent and immediate next steps, you can follow this issue describing the current state of work.

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. Screen

With the new Widget screen moved out of experimental status last month in Gutenberg 8.9, lots of work has gone towards addressing the feedback that’s come in as people have begun exploring this new screen. Right now, inclusion in 5.6 depends on the state of the Widget Screen before Beta 1 on October 20th. In an effort to successfully have this feature included in 5.6, efforts that were previously put towards the Navigation Screen are now being redirected here. As a result, expect that this area of work will be a big focus and decision point for the month ahead.

Along with handling any additional feedback that comes in, the following are specific items that will be worked on:

Deciding a path forward for how best to handle customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. & the widget screen interaction.
Creating updated designs for an improved user experience.
Exploring how third party widgets can be integrated.
Ensuring only superadmins can store HTML using the new 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. endpoint.
Addressing a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) feedback around improving the navigation tool.

Join the Widgets Screen weekly meeting:

In light of the decision mentioned above, the previous meeting on the Navigation Screen project will now focus on Widgets. As a reminder, the meeting happens in #core every Wednesday at 7AM UTC. These meetings will be focused on triaging issues 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/ with the [Feature] Widget Screen label and discussing any big structural issues.

Help with testing:

As part of the vision for the Widgets Screen to ease adoption for everyone, modernize the experience outside of just site editing, and upgrade what’s possible by enabling third party extensibility, feedback is still needed to help this become a reality. If you haven’t had a chance to yet, please follow this call for testing and share any bugs or enhancements on GitHub. Thank you to everyone who has given feedback already and helped move this work forward!

Follow along:

You can follow the progress of this work on this project board and by joining the weekly chat in #core every Wednesday at 7AM UTC.

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue iterating over the coming months. Currently, 5 out of the 6 milestones for site editing are marked as In Progress with overview tracking issues created for each milestone to better plan next steps. With that said, work this month will continue to focus on finishing up Milestone 1 – Site Editing Infrastructure and UI and Milestone 2 – Site Editor Navigation. As in prior months, it’s expected that this work will continue into the months ahead:

Group document settings in the 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..
Move templates and page navigation into the main W sidebar.
Design Explorations for a new sidebar showing template navigation.
Allow browsing all templates and parts.
Incorporate “Add New Page” Flow into “Add Template”.
Implementation is underway to build missing functionality for the query block as part of milestone 5.
Design explorations for Custom Post Type and taxonomies filtering for the Query block as part of milestone 5.
Enhancements to Post blocks (like Post Featured Image) to support more display options.

We’re watching the Theme Experiments repo as well to see how themers are attempting to build block-based themes. Please continue to share there and know we appreciate it!

Follow along:

You can follow the progress of this project on this project board. To help break down this work more, a new overview issue with key milestones for site editing was also created. For each major milestone, there are related issues for each milestone that are recommended to follow if you want a more granular look at each next step (example from Site Editor Navigation).

As a reminder, if you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more.

Areas to be aware of:

There’s a new experimental light box wrapper API that allows for a new way to define blocks in order for the markup in the editor to match the front end. While documentation is planned, it hasn’t been written yet. In the meantime though, you can check out the current PRs as this is now ready to be used by plugins: creating edit/save symmetry and stabilizing the API.

Theme Developers:

@joen did a wonderful show & tell session including in progress work on a Full Site Editing theme.

Additionally, any theme authors experimenting with Full Site Editing should check out the post from @aristath on a New JSON structure for FSE theme.json files.

Ways to Get Involved:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. In particular for this month, focusing efforts around testing the Widgets Screen would be very helpful and high impact.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

Core Editor weekly @ 14:00 UTC in #core-editor focused on all things Gutenberg.
Widget Sync weekly @ 07:00 UTC in #core focused on triaging and discussing Widget Screen work.
Block Based Themes meeting twice monthly at Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

#core-editor #gutenberg-next

annezazu 2:52 pm on September 3, 2020
Tags: accessibility ( 55 ), core ( 560 ), core-editor ( 703 ), gutenberg-next ( 23 ), themereview

What’s next in Gutenberg? (September)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for September. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Global Styles & Editor focused APIs

Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. Currently, the hope is that work on editor focused APIs can be wrapped up in the month ahead if all goes well. Some of this work will include the following:

Adding support for themes to control the editor in a global context.
Adding a global styles sidebar so users can begin to tweak styles.
Providing support for enabling/disabling custom gradients using 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..

Follow along:

You can follow the progress for this overall system in this overview issue. For more recent and immediate next steps, you can follow this issue describing the current state of work.

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. Screen

After months of work, this new screen has been launched out of experiments in the latest Gutenberg 8.9 release. This should allow for plenty of time for feedback before the 5.6 release. With blocks firmly paving the way for the future, this work on the widget screen is meant to help modernize the experience outside of just site editing, ease adoption for everyone, and upgrade what’s currently possible by enabling third party extensibility. This vision can’t be accomplished without feedback so please test and share any bugs or enhancements on GitHub. Work this month will include the following along with the feedback received from users:

Creating updated designs for an improved user experience.
Enabling the Global Inserter to be open by default for the widget screen.
Exploring how third party widgets can be integrated.
Refactoring the widgets screen to use the sidebars endpoint.
Fixing the legacy widgets preview experience.
Ensuring only superadmins can store HTML using the new 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. endpoint.
Addressing a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) feedback around proper labelling, improved navigation tool, and more.

Follow along:

You can follow the progress of this project on this project board.

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue iterating over the next months. Keep in mind that much of this work relates to other areas like Global Styles & Editor Focused APIs! With that in mind, work this month will mainly focus on the following based on the Milestone 2 – Site Editor Navigation. Note that timing for this work will likely need to be adjusted depending on progress made meaning this work might start in September but continue going forward.

Group document settings in the 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..
Indicate current template and template part when in site editor.
Move templates and page navigation into the main W 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..
Allow browsing all templates and parts.
Incorporate “Add New Page” Flow into “Add Template”.
Begin exploring missing functionality for the 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. as part of milestone 5.

We’re watching the Theme Experiments repo as well to see how themers are attempting to build block-based themes. Please continue to share there and know we appreciate it!

Follow along:

As a reminder, if you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more.

Navigation Screen

Similar to the Widget Screen, efforts have begun to launch this new screen to the world in order to gather more feedback. Right now, this effort has a few blockers but, if you’re able to, testing this screen and reporting feedback would be a huge help (Install Gutenberg and head to Gutenberg > Experiments to enable this screen). The aim is that this new screen will help expand what’s possible with menus while bringing block functionality to yet another part of WordPress in order to allow for more adoption and to offer a more modern experience.

Introducing the new Navigation editor to the world.
Sharing ideas for solving nesting in horizontally constrained spaces.
Sharing ideas for drag and drop in the navigation block on the navigation screen.
Building out navigator drag and drop.
Improve search results when adding a link.
Exploring in-toolbar link editing.
Exploring a fresh design for the Navigation Screen experience.
Adding variations for custom post types and taxonomies.
Update what the search block supports in navigation.

Follow along:

You can follow the progress of this project on this project board, review the overview issues (Block Navigation, Navigation Screen) & join the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat.

Areas to be aware of:

Since the block directory is still a new feature in the WordPress world, the following includes the prior links once more along with two additional issues to chime in on:

Block Creation tutorial that teaches you how to write a block plugin.
Block Submission tutorial that gives some tips and suggestions for ensuring your block is ready for the Block Directory.
Block Checker tool which will help you discover any issues that might prevent your plugin from working.
Share your thoughts around introducing the Navigation screen.
Review the current ideas for adding 3rd party widgets to the editor.

Theme Developers

Review the latest Gutenberg Themes roundup and, in particular, check out @tomjin’s PHP theme template compatibility proposal as it relates to Full Site Editing. Please chime in with your thoughts! Outside of this proposal, here are two other items that might be of interest:

Review this PR on allowing themes to opt into the new block based widgets screen now merged in Gutenberg 8.9.
Dig into the Block Based Theme tutorial to help you get started with building your own.

Ways to Get Involved:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. Focusing efforts around Widgets and Navigation in particular this month would be very helpful as both screens are on their way to no longer being experimental features.

Meetings to join:

While you can view all meetings here, here are specific meetings that touch on Gutenberg development to join depending on your interest and availability. Remember that you need a WordPress.org slack account to participate:

Core Editor weekly meeting on Wednesdays @ 14:00 UTC in #core-editor focused on all things Gutenberg.
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) weekly meeting on Fridays @ 15:00 UTC in #accessibility focused on wrangling accessibility related work across Core and the block based editor.
Navigation Sync weekly meeting on Wednesdays @ 07:00 UTC in #core focused on triaging and discussing Navigation screen work.
Block Based Themes meeting twice monthly on Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

#core-editor #gutenberg-next

annezazu 5:51 pm on May 20, 2020
Tags: core-editor ( 703 ), full-site editing ( 15 ), gutenberg ( 473 ), themereview

Ways to keep up with Gutenberg & Full Site Editing (FSE)

As work on Full Site Editing continues, it’s important that communication around the project is made explicit so everyone can follow along appropriately. Each person will have their own unique needs in keeping up with a project of this scale so what follows is more of a catalogue of ways to keep up rather than a recommendation for how to do so.

Yearly:

The WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Roadmap with Four Phases of 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/ updated by @chanthaboune and/or @matt. This is the highest level overview of the changes coming to WordPress.

Quarterly:

Quarterly Updates from Contribution Teams, coordinated by @chanthaboune. These updates give an overview on what each team is working on, struggling with, and how to get involved.

Monthly:

“What’s Next In Gutenberg?” posts. These updates are wrangled by the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor team and highlight what’s planned for the coming month of work on Gutenberg.

Block Based Themes Chat. These chats are currently wrangled by @kjellreigstad 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 and are dedicated to sharing FSE changes that will specifically impact themes. Agendas and summaries are shared on the make/themes blog.

Biweekly:

“What’s New In Gutenberg?” posts. These updates are wrangled by the Core Editor team and focus on what’s been released in each biweekly Gutenberg release. Currently, they tend to mimic a changelog.

Weekly:

Core Editor chats. These chats are wrangled by volunteer members in the #core-editor Slack channel. Agendas and summaries are shared on the make/core blog. They focus on task coordination and relevant discussions around Gutenberg releases. There is an Open Floor period in each chat where people can suggest topics to discuss.

Weekly Theme Related Gutenberg Updates (new initiative) wrangled by @kjellr. These posts are focused on themes, including everything from current discussions to recent changes, as well as helpful resources for theme authors.

Daily:

Checking in on FSE PRs and FSE issues on 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/. This will give you a nearly real-time understanding of what’s being worked on by the developers and designers.

Each of these are reliable ways of keeping up with the ongoing work on the new Full Site Editing feature coming to WordPress. A big thank you to everyone helping with these various initiatives!

Feedback welcome

What kinds of updates or communication might be missing? What might make these current updates and chats easier to follow? Share your ideas and feedback in the comments below! A next step to this work will be refining these communication pathways based on the feedback collected here and elsewhere.

Thank you to @itsjusteileen @andreamiddleton @paaljoachim @mapk for giving me feedback on this post.

Changelog

Oct 26th 2021: Updated title to include Gutenberg and removed reference to Weekly Gutenberg Design Updates.

#full-site-editing, #gutenberg

Paal Joachim Romdahl 9:05 pm on January 29, 2020
Tags: core-editor ( 703 ), core-editor-summary ( 185 ), gutenberg ( 473 ), meeting notes ( 227 ), summary ( 817 ), themereview

Editor chat Summary: 29 January, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 29th January 2020 held in Slack. Moderated by @youknowriad.

Weekly Priorities

@jorgefilipecosta
We are getting closer to the WordPress 5.4 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. releases.
Release dates:
11 February 2020 – Beta 1 – Deadline for new features (after this date, only 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 for regressions in the release).
18 February 2020 – Beta 2
25 February 2020 – Beta 3
3 March 2020 – RC1
10 March 2020- RC2
17 March 2020 – RC3
24 March 2020 – RC4
31 March 2020 – 5.4 Release day

The main priority is making sure we don’t send an unfixed critical issue on the first WordPress 5.4 beta. To track the issues we have a project board:
https://github.com/WordPress/gutenberg/projects/39
We should give particular care to issues raised after 18th of September (date of the last 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/ release that was included in WordPress 5.3).

@youknowriad
Gutenberg 7.4 on Feb 5 (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). on Feb 3)
(Exceptional release) Gutenberg 7.5 on Feb 12 (RC on Feb 10)
Both will be included in WP 5.4.
What do you think about the current state of things?

@jorgefilipecosta
Currently it seems we are on track. Some new features like the custom gradient picker may need some focus to be polished and could benefit from tests/feedback. https://github.com/WordPress/gutenberg/issues/16662 and https://github.com/WordPress/gutenberg/pull/19582
I would also like to request everyone that implemented experimental 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.’s to think if they could be made stable before WordPress 5.4. It would be good to reduce experimental API’s as much as possible.

I will soon add a comment on https://github.com/WordPress/gutenberg/issues/17743 pinging the authors of API’s I think could be stabilised.

@gziolo
We are discussing with @mcsf 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. variations. It is nice to have for 5.4.
I believe that Social Icons is still not exposed for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. so we only would include this new API paired with Social Icons block.

I also don’t feel that we can make the accessible toolbar for 5.4 but maybe it’s better to have it enabled together with the block toolbar redesign. In the gist, it’s change in the tabbing behavior where every toolbar is only one tab stop and you can navigate between items with arrow keys, home, end, etc. Super important from 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) standpoint.

@mkaz
We started a draft PR iterating on Social Icons adjust implementation to allow for no-duplication of assets and making extendable, but there are some trade-offs being considered:
https://github.com/WordPress/gutenberg/pull/19888

Task Coordination

@karmatosed
I’ve had my head deep in Figma working on global styles. Focusing on the minimum version first. I also have been diving into controls. I also have been working on some iterations to color picker. Along the side there is as always a constant flow of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..

@youknowriad
Still working on the Dashicons and gathering all icons under the same package. Wrote some blogblog (versus network, site) posts about Gutenberg Extensibility APIs and Modularity. https://make.wordpress.org/core/2020/01/23/controlling-the-block-editor/
Reviewing, triaging as I can.
I’m hoping to continue on the icons and to circle back to the keyboards shortcuts package work as there’s still some improvements to make to allow third-party shortcuts to show up in the modal.

@jorgefilipecosta
Last week:
I started the work on the global styles, proposed the resolver system.
Iterated on the angle picker and merged it.
Triaged issues relevant for WordPress 5.4 & submitted bug fixes.
Next week:
Audit experimental APIs. Stabilize some API’s I proposed.
Audit dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and create an issue summarizing all the dev notes needed.
Continue the work on global styles.
Continue the work on the custom gradient picker.
Continue the WordPress 5.4 preparations by triaging and fixing issues.
PR reviews.

@andraganescu
I am working on adding features to the author block.
https://github.com/WordPress/gutenberg/issues/19696 and
https://github.com/WordPress/gutenberg/pull/19894

@mkaz
We have some cool image editing tools we’d love to get in at some point, appreciate some feedback and guidance. Issue and details added here, 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 available for testing: https://github.com/WordPress/gutenberg/issues/13748#issuecomment-574903126

@aduth
Been working a fair bit around the LinkControl component and related implementations (Popovers, etc). I expect to be continuing this in the next week.
Discussing user preferences persistence using 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.. There’s been a lively discussion in https://github.com/WordPress/gutenberg/pull/19177

@nosolosw
I’ve also been diving into GlobalStyles (master issue at https://github.com/WordPress/gutenberg/issues/19611) pairing with Jorge and Q. My focus at the moment is accommodating the prototypes shared in the issue into the proper data structures, client side.
Need a tech review at https://github.com/WordPress/gutenberg/pull/14930

@gziolo
Merged create-block package for block scaffolding, still not published to npm until next Wednesday.
Landed Variations API integration with the inserter.
Some more work to improve the workflow for syncing Gutenberg and WP core.
I plan more work on the Variations API and smaller accessibility improvements I started earlier.

@mcsf
I have been focusing on the Block Patterns Variations API with @gziolo and exploring applying that to Social Links: https://github.com/WordPress/gutenberg/pull/19887
Discussing what @epiqueras initially proposed of server-side rendering support for parent attributes context:
https://github.com/WordPress/gutenberg/issues/19685
Improved the way RichText blocks do or don’t automatically transform content into another block: https://github.com/WordPress/gutenberg/pull/19727

@itsjonq
Continue with Global Styles work. Pairing with @karmatosed, @nosolosw, and @jorgefilipecosta for various parts. Also diving deeper into the technical aspects/flow and planning.
https://github.com/WordPress/gutenberg/issues/19611
Updates to the RangeControl component in wordpress/components at https://github.com/WordPress/gutenberg/pull/19916

@richtabor
Background color support for Columns block has landed: https://github.com/WordPress/gutenberg/pull/17813
Tidied up labels/titles to use sentence case formatting: https://github.com/WordPress/gutenberg/pull/19903 and https://github.com/WordPress/gutenberg/pull/19901

Open Floor

@SvenWeber asked about this issue: https://github.com/WordPress/gutenberg/issues/19898
@aduth added a comment to the issue.

@Munirkamal asked:
How can I replicate the “Add to Reusable Blocks” functionality on my custom Gutenberg Block which I need to allow users to save to a 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.. So users will be able to save the block to a defined post type like core add to reusable functionality.
@epiqueras
I think he means saving the blocks to a different CPT.
https://github.com/WordPress/gutenberg/blob/5cb272724b30877217c9ec2d6ee0f4724deb4b51/packages/block-library/src/template-part/edit/index.js#L39
https://github.com/WordPress/gutenberg/blob/5cb272724b30877217c9ec2d6ee0f4724deb4b51/packages/block-library/src/template-part/edit/inner-blocks.js#L8-L21
@youknowriad
You just need to save a wp.blocks.serialize( block ) and save as “content” of your CPT.

@kjellr
A brand new recurring meeting in the #themereview channel. It’s dedicated to crafting the future of block-based themes in concert with the full-site editing work happening in Gutenberg. It will be held bi-weekly on Wednesdays @ 16:00 UTC, beginning Feb 5th. Look for an official post about the meeting on make.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//themes later today.

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

Welcome!

Communication

Announcements

Key Project Updates

Task Coordination

Open Floor

Announcements

Monthly Priorities & Key Project Updates

Task Coordination

Open Floor

Preparations for WordPress 5.7

Global Styles

Full Site Editing

Areas to be aware of:

Ways to Get Involved:

Global Styles

Blocks in the Widget Screen

Blocks in the Customizer

Full Site Editing

Areas to be aware of:

Ways to Get Involved:

Addressing WordPress 5.6 feedback

Global Styles

Full Site Editing

Areas to be aware of:

Ways to Get Involved:

Preparations for WordPress 5.6

Full Site Editing

Overview

Global Styles

Ways to Get Involved

Meetings to Join

Global Styles & Editor focused APIs

Full Site Editing

Areas to be aware of:

Ways to Get Involved:

Global Styles & Editor focused APIs

Full Site Editing

Navigation Screen

Areas to be aware of:

Ways to Get Involved:

Feedback welcome

Weekly Priorities

Task Coordination

Open Floor