The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in our bug tracker.
We use Slack for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.
Our core development meetings are every Wednesday at 05:00 UTC and 20:00 UTC in the #core channel on Slack. Anyone can join and participate or listen in!
This monthly update contains the high-level items that GutenbergGutenbergThe 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 April. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.
Work on the blockBlockBlock 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 WidgetWidgetA 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 is a continued focus for the month ahead. This effort aims to bring the flexibility of block editing to the widgets and customizerCustomizerTool 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. The current efforts include:
You can find more information about the current work in progress in this tracking issue, as well as on this project board. Moreover, you can join #feature-widgets-block-editor in WordPress.orgWordPress.orgThe 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/SlackSlackSlack 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 Editor-focused meetings.
Navigation Editor
Like the Widgets Editor, the Navigation Editor aims to help expand what’s possible with menus while bringing block functionality to yet another part of WordPress to allow for more adoption and offer a more modern experience. Because the Navigation Editor needs to work nicely with the Navigation block (and vice versa), much of the current effort from contributors focus on the Navigation block. With this in mind, current efforts include:
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:
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.
Block & PluginPluginA 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:
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Blocks can now load JavaScript in the frontend on demand.
We’re still watching the Theme Experiments repo to see how theme developers are building block themes. Please continue to share there and know we appreciate it.
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 triagetriageThe 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 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.
GutenbergGutenbergThe 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/10.3.1 release shipped on April 1st.
Making the margins the same between frontend and backend (no opinionated margins provided by the blockBlockBlock 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 by default).
Block Supports: added a gutenberg_block_has_support helper function and support for padding in dynamic blocks 30322, border for search block #30227.
Fixes: title in the save panel of the site editor 30521, fix for themes without theme.jsonJSONJSON, 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. support but with experimental link color support 30452.
Theme.json: Update format #29891, there’s now a draft PR at #30541, conversation about whether and how to expand the use of CSSCSSCascading Style Sheets. Custom Properties #29714
Updates and improvements keep chugging along! The dependency on responsive nav will likely get merged today, and then the responsive PR can move forward. A new update attempts to fix the HTML produced by the block. This is blocked by the lack of advancement in the discussions opened by @talldanwp (Issue30007 and Issue30006). Any help moving those points forward would be greatly appreciated! Plenty of other refinements and updates continue too, for example the placeholder state was updated. The best way to follow along is by labels in GitHubGitHubGitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ PRs or this tracking issue.
The Block based Navigation editor is advancing with a host of PRs aimed at polishing various functionality (PR30374, PR30403, PR30524 , PR30340) and some that could use a review and testing (PR30446, PR30440, PR30349).
WidgetWidgetA 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 from @andraganescu
Block based Widget Editor work is focused on tidying up blocks in customizerCustomizerTool 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. for better accessibilityAccessibilityAccessibility (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) and various bugs.
Started doing PR reviews by testing and adding comments. Hopefully, this can help the “Gutenberg CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.” team a little bit.
Currently figuring out the best way to filterFilterFilters 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. PRs for reviews.
I’d love feedback on the approach in this PR for 24337, please. If it seems appropriate, I can built it out for the rest of the existing blocks that support the feature, but thinking it’s possible this change should happen higher up somewhere so that blocks don’t have to adjust for it.
I’ve mainly focused on the FSE Outreach Program responding to the current call for testing and pausing to get some feedback for how to improve the program.
I plan to ship another call for testing shortly after this current one ends alongside a summary post.
I want to experiment tomorrow too with holding a friendly, casual zoom call for about 30-45 min to talk through some fun FSE issues/designs/PRs that have caught my attention! Join #fse-outreach-experiment to stay tuned if that’s of interest.
Next week I will probably keep working on the same things: FSE MVPMinimum Viable Product"A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia & hybrid-themes.
I’ve been continuing on the Navigation block, polishing and polishing. While it’s in a good place, it’s opening up some grand questions about the next steps, all exciting ones. And I’m excited to delve into patterns for it as soon as I can.
Open Floor
Are there any updates for a home/name for Site Editor Documentation? Raised by @poena.
Carolina brought up a previous post from early February asking whether there was an update around the name and place for documentation as currently it’s causing blockers/confusion for how to proceed. Currently, the documentation in the block editor handbook that’s related to FSE is in several places and pretty difficult to find. At the same time, as interest grows around FSE, people are seeking out more information. For example, one of the concerns that Carolina shared was around how if the documentation is in the theme developer handbook or the block editor handbook, it will be difficult to find and likely not visible enough for when a large number of people are first introduced to FSE. Carolina then passed along a suggestion to have a “front page” with basic explanations of the key concepts that then guides visitors to user or developer docs depending on their interests.
After some back and forth discussion, a loose consensus was reached on the following:
The lack of a decision around name and placement shouldn’t stop us from creating docs and organizing them properly when these things get clarified.
The go/no go dates should provide clarification this month around what needs to be documented first.
An introduction page that can guide people curious about FSE likely needs to be created or at least explored.
Exploring renaming the “Block Editor Handbook” to something more general might help alleviate some of these concerns by making the Handbook more flexible to allow for FSE items.
Next steps: @mkaz will kick off a discussion for renaming the handbook and create an issue for an initial intro FSE page to direct people.
WordPress 5.7.1 maintenance release. The following release schedule is being proposed: Release Candidaterelease candidateOne 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).: Wednesday 7 April, 2021 around 23:00 UTC. Final release: Wednesday 14 April, 2021 around 23:00 UTC.
GutenbergGutenbergThe 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/ 10.3
This week’s status report: ongoing work for the major tasks necessary for the MVPMinimum Viable Product"A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia.
Navigation BlockBlockBlock 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 third round of testing finished last week and a summary post was added highlighting various issues found while people created wonderful, custom 404 pages.
There is another call for testing, building a restaurant themed header that hopefully will be both equally as fun and full of new insights about how to enhance the FSE experience.
Mainly focused on FSE Outreach program (daily fse testing, reporting issues, writing up summaries, writing tests, amplifying!) and a few CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement post ideas in the pipeline.
Reporting issues and creating pull requests toward the FSE MVP.
Open Floor
Discussing the Full Site Editing MVP. To summarize the discussion that happened during the meeting and after, here are the top takeways:
There is confusion of what MVP for Full Site Editing consists of.
As has been previously shared, the MVP should make it possible to build a version of the Twenty Twenty-One theme, using only blocks, without any coding knowledge.
Widgets & Navigation work are not included in FSE but they are seen as complementary projects to help with adoption.
At the moment we have two targets: the full site editing MVP & what would be introduced in 5.8.
The first quarter of the year is coming to an end, and with it, GutenbergGutenbergThe 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/ 10.3 comes as well! This release brings us some important changes to Global Styles, as well as several improvements to blocks such as the Navigation blockBlockBlock 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., enhancements to the inserter, an editor performance boost, and even a few new blocks! As always, many bugbugA 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 are included, too.
Improving the Block toolbar
In order to provide a consistent UIUIUser interface across blocks, blocks have seen their toolbars rearranged following a standard grouping layout. While the last release saw the Image block have its toolbar standardized, this time a whole set of blocks have been normalized as well, including blocks such as Button, Buttons, List, Heading, Paragraph, Quote, Audio, File, Media and Text, Video, Site Logo, Cover, and Post Featured ImageFeatured imageA 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. blocks.
Introducing layout configuration in theme.jsonJSONJSON, 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.
Themes have always had the responsibility of defining alignments in the frontend through CSSCSSCascading Style Sheets. rules. They also define different widths for both the editor and frontend. The content width, whether they support wide alignments or not, and the CSS to support all these combinations can be very hard to write properly.
With Full Site Editing, the templates are written in blocks and edited in the site editor. This means that the editor has to match the front end as much as possible while allowing theme authors to tweak these alignments and widths in the editor. If this doesn’t happen, it causes confusion and frustration as seen in the feedback from the FSE Outreach Program.
To address these requirements and to simplify the way themes define and style alignments, Gutenberg 10.3 introduces the concept of layout and layout configuration, a feature automatically enabled when you rely on a theme.json file (experimental-theme.json file at the moment).
Theme authors should be able to make use of this feature by adding a layout config to their theme.json file and indicating in their block templates which containers inherit that config. The layout config is also automatically applied to the post editor.
If you’re using the experimental theme.json file already, you should be able to follow these two pull requests that update the empty theme and the twenty twenty-one blocks theme to use this feature.
Changes in theme.json block supports and supported styles
Block supports are no longer used to decide whether the styles in the theme.json file for a block should be used or not. However, block supports are still used to show UI controls in both the block & global styles sidebarSidebarA 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., but themes can now use any theme.json style property that exists in any block:
New “Theme” categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. (left); multiple keywords in the slash inserter (right).
More theme blocks
With the goal of providing classic template tagtagA 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.) features with blocks, up to three new blocks are introduced in this release. The LogIn/Out block is now available to provide login and logout links. Optionally, it can display the login form instead of a link by setting the available block attribute.
Two new blocks for archive pages are also available. The Term Description block displays the description of categories, tags, and custom taxonomies. On the other hand, the Archive Title block displays the title of the archive itself.
Login/Out block (left); Archive Title and Term Description blocks as seen in the editor (right).
Cover block improvements
The Cover block now supports drag and drop for replacing the background image.
Editor performance improvements
In recent releases, the time it took for the editor to load increased slightly due to the growing number of patterns available in the Inserter. Gutenberg 10.3 fixed this so that the editor performs well regardless of the number of available patterns!
10.3
Enhancements
Add since versions to the deprecated features. (30072)
Blocks: Add “theme” category and better present Template Parts in the inserter. (30020)
Open adminadmin(and super admin) sidebar menu over editor on small screens. (29955)
Block Library:
Cover: Allow drag and drop media replacement. (29813)
File: Make the editor markup match the frontend. (30148)
Social Links: Improve selected state of empty block. (29756)
Standardize the groups in the block toolbar. (30012, 29247, 29863)
Verse block: Add support for the padding to the verse block. (29820)
Components: Allow multiple words in the autocomplete phrase matcher. (29939)
Gutenberg PluginPluginA 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: Improved cache bust without filemtime for assets. (29775)
Icons: Hint the lowercase icon by 0.15px to correct the font weight appearance. (29754)
Media: Use image default size from settings. (29966)
Fix regressionregressionA 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. with multi select style. (30128)
Fix the issue with block style preview when example missing. (29894)
Fix sibling block inserter displaying at end of block list. (29920)
Revert showing empty paragraphs on fronted. (29809)
Show the active block variation’s icon in Select mode. (30143)
Blocks: Adding onRemove event to verse block. (30104)
Block Library:
Cover: Improve disabled media buttons check for placeholder. (29858)
Embed:
Fix overzealous aspect ratio scaling for embeds. (29510)
Fix block reset sizes on external URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org change. (26879)
Update the layout alignment description for better clarity. (29974)
Gutenberg Plugin: Update “requires at least” value to 5.6. (29646)
E2E Tests: Stabilize randomly failing tests in trunktrunkA directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. (29836)
Navigation Component: Align item text to the left/right. (30083)
CustomizerCustomizerTool 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.: Add widgets customize inspector. (29755)
Full-Site Editing:
Add a layout configuration to the Group block and theme.json and make alignments declarative. (29335)
Add client ID trees selectors in block navigation. (29902)
Add description field to Post Content block. (29971)
Add preload_paths filterFilterFilters 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. for widgets screen and full site editing. (28701)
Add support for experimental layout in Post Content block. (29982)
Add layout support to the Template Part block. (30077)
Add link color option in Site Title block. (29924)
Automatically open the sidebar to the appropriate menu. (26964, 30098)
Close navigation panel after template selection. (29956)
Expose Template Part block variations to the Inserter. (30032)
First step towards hybrid themes – fallback to PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher templates. (29026)
Fix block toolbar from overlapping navigation panel. (29918)
Fix different markup in the editor and on the frontend for the Site Title block. (29021)
Fix edge case where the default layout could be undefined. (30024)
Fix persistence of Preferences in site editor. (30019)
Fix Query LoopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. block margin. (30078)
Remove alignments from the root level of the site editor. (30079)
Remove headerHeaderThe 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. toolbar transition in reduced-motion mode. (29764)
Remove unused QueryProvider in Query block. (29947)
Template Part: Identify template parts in error messages. (28398)
Increase importance of submenus staying open. (30169)
Keep submenus open on select in the editor. (29713)
Match editor markup to rendered in Navigation Link block. (29935)
Move theme location settings to navigation editor sidebar. (29458)
Navigation MenuNavigation MenuA theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site.: Show submenus only on select in the editor. (29869)
Unset font weight and text decoration inheritance in Navigation block. (30011)
Use the interface package for the navigation screen. (30013)
Visual and design improvements for List View. (29769)
Widgets Editor:
Fix warning when widgets block editor is disabled. (30318)
Iterate on widgets REST APIREST APIThe 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/. endpoints. (29649)
Load block editor assets in the navigation and widgetWidgetA 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. editors. (30076)
Unify menu item styles for Navigation Block and Page List blocks. (29975)
Use a default sans serif font for the widget screen. (30084)
Remove superfluous sentence in create block tutorial. (30062)
Update block design principles with a new section on how to group controls. (29816)
Update broken link to Getting Started for the ReactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native based Mobile Gutenberg. (30162)
Update the quick view image on the documentation homepage. (29808)
Editor: Clarify the purpose of the @wordpress/editor package. (30136)
I18ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Replace dead link in README.md. (29699)
Interface: Fix typos in interface package. (29740)
Code Quality
APIAPIAn 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:
Move is-typing and is-outline-mode classes up the tree. (30106)
Move nav mode exit from writing flow to block props. (30175)
Block Library:
Refactor ServerSideRender to use React hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.. (28297)
Remove obsolete editor styles for List block. (30094)
Set delay to zero in the reduce-motion mixin and tests. (29762)
Eslint Plugin: Add TypeScript as peer dependency and make it optional. (29942)
GitHubGitHubGitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Workflows:
Use Gutenberg token for version bump, changelog commits. (30212)
Packages: Enforce version bump for production packages after WP major. (29903)
Unit Testing: Allow TypeScript modules for transpiled packages. (29873)
Performance Benchmark
The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.
Version
Loading Time
KeyPress Event (typing)
Gutenberg 10.3
4.90s
31.86ms
Gutenberg 10.2
5.15s
31.41ms
WordPress 5.7
4.88s
25.24ms
Kudos to all the contributors that helped with the release! 👏
There’s something magical about finding the exact blockBlockBlock 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. you want exactly when you need it. When the Block Directory came to WordPress in 5.5, the aim was to allow a seamless way to add individual block plugins so you can create what you want when you want without ever leaving the editor. In GutenbergGutenbergThe 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/’s 10.2 release, to build on that foundation, you will now still get results from the Block Directory even if you have a block already available that might do the trick. This helps surface even more options so you can find the perfect fit. Inspired by having more time to read books, check out the example below to see how the experience has changed!
Before
After
If you find yourself searching and still unable to find the block you’re looking for, consider creating and submitting your very own block pluginPluginA 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 to the directory to be found and used by anyone using WordPress 5.5+! Be sure to check out the guidelines and the block tutorial to get started.
In case you missed the first post on post/page performance, I’d recommend checking it out first before digging into this post, as it helps give greater context into the breadth of work around performance improvements. This post builds on the discussion by talking specifically about the approach Core ContributorsCore ContributorsCore contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. take to managing the performance of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor itself!
Think of Core Editor Performance as impacting the user experience when creating content. It’s the difference between a jarring experience, with the editor barely keeping up as you type, and a creative one — where adding dynamic content is a breeze with performance hardly being noticeable.
With each release of GutenbergGutenbergThe 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/, a performance benchmark is run against the last few releases that compares different response times for a large post (~36,000 words, ~1,000 blocks). You can find this benchmark at the bottom of each “What’s New in Gutenberg” post. While this approach doesn’t cover every scenario, and absolute numbers are not intrinsically meaningful, it has helped identify variations in performance for different releases. Generally speaking, while the loading time of the editor is important, pay special attention to typing speed (also known as KeyPress Event speed). This is a far more important measure when it comes to user experience as this is what allows for the smooth experience when working in the editor.
Beyond an overview of neat numbers, what does focusing on Core Editor Performance entail? Pulling from the documentation, the following overall metrics are tracked:
Loading Time: The time it takes to load an editor page.
Typing Time: The time it takes for the browser to respond while typing on the editor.
BlockBlockBlock 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. Selection Time: The time it takes for the browser to respond after a user selects a block. (Inserting a block is also equivalent to selecting a block. Monitoring the selection is sufficient to cover both metrics).
It’s that time of the fortnight again: We’ve just published a new release of GutenbergGutenbergThe 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/! Version 10.2 brings to you a number of additions to Full-Site Editing (FSE) and Global Styles, and a sizeable list of improvements to the editing experience, as well as bugbugA 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.
Offering Patterns on BlockBlockBlock 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. setup
Introducing some initial explorations on how specific patterns can be better surfaced from a block’s placeholder state. Upon inserting a Query block there’s now a setup step that allows picking a block pattern for it to use. This allows users to start with a good design basis. Note that this goes beyond what block variations afford, as it’s an APIAPIAn 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 can directly connect with a block pattern categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.. The candidate block patterns are fetched via a new API that allows querying for patterns that include a given block type.
Alternatively, the user has the option to “start empty”, in which case they’ll be able to choose from the existing CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. block variations (e.g. Title & Date, Title & ExcerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox., etc).
Spacer Block width can be adjusted (in Navigation Block)
When inserted into a parent block that dictates a horizontal orientation (such as the Navigation Block), the spacer block’s width (rather than height) can now be adjusted. This makes some new cool customizations possible on horizontally-stacked blocks.
Transform Media & Text to Columns
It has been possible for a while to transform any single block into a Columns block (with a single column). For the Media & Text block, that behavior is unlikely to produce the desired outcome. Thus, when transforming a Media & Text block into a Columns block, it will now result in two columns (and all the relevant fixings from the original block).
Hide writing prompt from subsequent empty paragraphs
Rather than showing the “Start writing or type / to choose a block” prompt in each of a number of subsequent empty paragraphs, we now only show it in the first one.
Add check for button text before rendering button block. (29717)
Skip CSSCSSCascading Style Sheets. minification via PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher. (29624)
Restore the margins of blocks relying on the figure element. (29517)
Components: Try to make the order of fills stable in regular slots. (29287)
Add expandOnFocus, showHowTo and validateInput experimental props to FormTokenField. (29110)
Hide writing prompt from subsequent empty paragraphs. (28275)
New APIs
Plugins: Add scoping functionality to the Plugins API. (27438)
The registerPlugin() function (in the @wordpress/plugins package) now accepts a scope argument that will limit that pluginPluginA 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 to be displayed only by <PluginArea /> components with a matching scope prop. See #27438 for more details.
Bug Fixes
Reusable Blocks:
Fix editor crash when converting block with visible styles to reusable (after a save and page reload). (29059)
Fix reusable block crash when converting a just created reusable block to blocks. (29292)
Yelp: Fix foreground color, make background transparent. (29660)
Social Links: Replace CSS variables with block context approach. (29330)
Table of Contents block:
Fix links when in archive loopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. or when using “Plain” permalink structure. (29394)
Fix inline block styles minification issues with calc(). (29554)
Packages: Update the publishing command for npm with next dist tagtagA 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.). (29379)
Ignore build folders when native unit tests. (29371)
Interface: Fix ReactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. warnings triggered in ActionItem component. (29340)
Search block: Add missing space to provide valid HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.. (29314)
Blocks: Ensure that metadata registered on the server for core block is preserved on the client (try 2). (29302)
Gallery Block: Fix the crop images setting. (29823)
Fix Error: Could not process the ‘wp-config.php’ transformation. (29800)
Performance
Revert “Block edit: Avoid memoized block context in favour of useSelect”. (29621)
Experiments
Global Styles:
Do not add padding sub-properties if there’s no values in theme.jsonJSONJSON, 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.. (29712)
Fix specificity conflictconflictA conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. of blocks with single classes as selectors. (29378)
Fix specificity issue between theme and user styles. (29533)
Custom Link Color: Do not apply to buttons. (29557)
Implement skip serialization for color key in style att. (29253)
Full-Site Editing:
Site Title: Add text decoration and text transform controls. (29622)
Prevent clicking on tag and category links in the site editor. (29583)
Print nothing in the front end if there are no results in Query block. (29521)
[Query block] Remove exclusion of current page id. (29432)
Handle missing categories/tags in Query block. (29424)
Query block setup with block patterns integration. (28891)
Update template descriptions for clarity and humanity. (29531)
i18ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Fix the template area unassigned type string. (29617)
Temporary hack to render blocks in customizerCustomizerTool 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.. (29365)
Fix shortcodeShortcodeA shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. not showing in the widgets screen. (29282)
Add NVDA instructions to the accessibilityAccessibilityAccessibility (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) testing documentation. (29312)
Component Systems: Update references to external module. (29233)
Docs: Add info about npm release types and their schedule. (29028)
Docs: Update slug for block-based theme tutorial. (25839)
Code Quality
Rename load_separate_block_styles to load_separate_block_assets. (29703)
Update the minimum WordPress version required by the gutenberg plugin too 5.6. (29701)
Components: Ensure that SlotFill does not use portals in React Native. (29631)
Block edit: Avoid memoized block context in favour of useSelect. (29333)
Tools
Scripts:
Fork jest-environment-puppeteer to use puppeteer-core directly. (29418)
Add TypeScript support to linting command. (27143)
Needs Info / Stale bot
Add stale issues bot to help triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. efforts. (29321)
Do not automatically close message, update stale message. (29310)
Docs/Tools/CI: Update references from master to trunk. (28433)
Various
Full-Site Editing
Site Editor: Browsing sidebarSidebarA 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. templates menu restructure. (28291)
Template part ‘area’ term – reword confusing ‘type’ terminology. (29679)
Add i18n support for template part variations’ descriptions. (29612)
Multi entity save panel – remove dynamic copy. (29637)
Table of Contents block
Add Table of Contents block (dynamic rendering + hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. version). (21234)
Deregister TOC block until issues are resolved. (29718)
Add regressionregressionA 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. test for editor JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. crash caused by rtlcss parsing exception, take 2. (29598)
Reset all WP Adminadmin(and super admin) styles in the wrapper of the editor styles. (29590)
Revert “[Mobile] – Fix splitting/merging of Paragraph and Heading”. (29587)
Try updating the minimum required WordPress version for the plugin. (29579)
Focus input when InputControl spinner arrows are pressed. (29305)
WP Block Styles: Only load in the editor if a theme opts in. (29252)
Add new overlay text icon, and use for image. (29215)
Add Missing URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org state to Navigation Link Block. (28861)
Improve the block editor handbook table of content. (28665)
RN: Add Bottom Sheet Select Control component. (28543)
RichText: Bypass paste filters for internal paste. (27967)
Block Directory: Update search results list UIUIUser interface. (25521)
Performance Benchmark
The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.
Version
Loading Time
KeyPress Event (typing)
Gutenberg 10.2
5.25s
25.8ms
Gutenberg 10.1
5.01s
23.1ms
WordPress 5.7
5.13s
22.3ms
Kudos to all the contributors that helped with the release! 👏
After a few months and a few rounds of testing for the Full Site Editing Outreach Program, this post summarizes the top pieces of feedback of the current experience to help inform ongoing efforts for an MVPMinimum Viable Product"A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia. Keep in mind that this post is simply a snapshot in time and is inherently going to leave out aspects of the experience that haven’t been the subject of calls for testing yet, for example, Global Styles. If you want a more in-depth look at feedback across the testing calls and a full summary of all issues rather than a sampling, please review the summary posts. If you want to help give feedback, join the calls for testing or test whenever you’d like.
While the saving experience was reliable technically and generally intuitive, it has left a lot to be desired and resulted in a fair bit of confusion around expected behavior. This is likely because multi-entity saving (saving multiple aspects at once) is a new WordPress concept and one that underpins every interaction in the Site Editor. Whether it was mentioning desired features, finding bugs, or confusion around how to accomplish a task, this proved to be a robust area of feedback.
The distinction between editing the entire site vs. specific content
Similar to the saving process feedback, this is another area where features technically work but are difficult to distinguish across the experience. For example, one can edit a template directly, but it’s not always clear when one is editing a template or editing an item of content. Beyond just clarity in what one is editing, there needs to be the right amount of friction when switching between content that impacts the entire site vs. content on an individual post/page. This is an area of active iteration and exploration to get the right amount of friction in place, as you can see in open issues like this one around clarifying template vs. content editing, and this one around refining the experience of editing a template part in isolation.
Rethinking Width/Alignment
Currently, alignment in Full Site Editing works to optimize traditional themes that provide their own alignment styles. This approach has served the project well until this point, but it’s a key area to reconsider to ensure a true and reliable WYSIWYGWhat You See Is What You GetWhat 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. Thankfully, work is already underway in an important PR by @youknowriad to reimagine how this dynamic should allow for more control over alignments/widths when using the Site Editor.
General Usability Improvements
As this work moves into a place of refinement, there are numerous enhancements to consider to improve overall usability of the Site Editor. This is a “catch-all” categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. but an important one nonetheless, as it will help the Site Editor experience move from functional to delightful. What follows is a sampling of items both to get a sense of the kinds of issues raised and the spread:
Placeholders for some of the newer blocks in the site editing experience prove to be both a powerful way to guide people and a point of confusion. This feedback mainly came into play with blocks like the Query Block (including the blockBlockBlock 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 like Posts Lists), Social Icon Block, Featured Image Block, and the Navigation Block. Each currently gets users started in different ways. In the long run, it seems that users will benefit from a standardized, consistent way to interact with placeholder content across all blocks. This is particularly important when viewed through the context of editing a template where you might mostly see placeholder content.
WordPress 5.7 was released on the 9th of March. Contains features such as various updates to the BlockBlockBlock 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, from HTTPHTTPHTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. to HTTPSHTTPSHTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in a single click, new Robots APIAPIAn 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., lazy-load iFrames and a lot more. A bit shout out to @noisysocks for his work as the technical Block Editor lead.
GutenbergGutenbergThe 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/ 10.2
Global Styles and mobile: Working on identifying tasks.
Block based WidgetWidgetA 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.
Check out the SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel #feature-widgets-block-editor and various Widgets Screen issues on GithubGitHubGitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.
Still focusing on making sure the experience is as WYSIWYGWhat You See Is What You GetWhat 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. as possible without requiring implicit theme styles.
Landing a PR to normalize “figure” element styles.
Then another one to reset the WP-Adminadmin(and super admin) styles properly in the editor canvas to avoid CSSCSSCascading Style Sheets. bleed as much as we can.
Would like to bring focus to this PR. Draft: Pulling JavaScript to the frontend from a Core Block. The PR will require enqueuing JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. on the front-end which has not been done from a coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. block before. The results of the PR can also help get an accordion block into Gutenberg. Associated merged PR should help enqueing assets.
Old project with new focus. To asynchronously load TinyMCE for the freeform block in certain circumstances. Need help in figuring out the particularities of how TinyMCE is integrated into WordPress core. I think it could be a huge performance win if we could offload TinyMCE from the initial page load.
In Progress: GSS support, Reusable blocks, removing ability to switch to the Classic editor, editor switch, dual-licensing Gutenberg, progress on Search block, progress adding search to the block inserter, progress on the embed block.
Blockers: We’re experiencing flakiness in the native mobile E2E tests, affecting many PRs and we’ll continue to work on fixing it.
Lots of feedback wrangling, issue testing, etc for the second call for testing with a draft in place for a summarized post.
Working on the next Core Editor Improvement post on the performance of the core editor itself.
Continued work on a “role of the gutenberg pluginPluginA 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” post to clear up some confusion (TBD on when that’ll launch).
Here is an associated metaMetaMeta 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.blogblog(versus network, site) post. In Progress: Scheduling updates to published posts on WordPress.org.
I’ve been helping with reviews, bugfixing, and getting inner blocks working on the quote block. My focus for next week is going to be quote plus tackling some tasks for global styles.
Open Floor
Announcement
@mikeschroder Gutenberg contributions are being prioritized by GoDaddy, so I’m spending time learning, and will be around the repo a bit more often. As part of that prioritization, I’m excited to welcome @mamaduka, who is joining the team full time for contribution to Gutenberg!
He was also wondering about releases and @annezazu shared https://make.wordpress.org/core/2021/02/11/making-wordpress-releases-easier/ Update: Let’s move forward with the March release, a July release (to give folks time to adjust their company plans), and a final release in December. I will create a plan to help us lessen the burden of releases, and in December I will see what we’ve accomplished and get some 2022/23 target release months published.
This monthly update contains the high-level items that GutenbergGutenbergThe 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 March. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.
BlockBlockBlock 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 WidgetWidgetA 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
Work on the Block-based Widget Editor (Widgets Screen) is a continued focus for the month ahead. This effort aims to bring the flexibility of block-based editing to the widgets and customizerCustomizerTool 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. The current efforts include:
Like the Widgets Screen, the Navigation Screen aims to help expand what’s possible with menus while bringing block functionality to yet another part of WordPress to allow for more adoption and offer a more modern experience. Because the Navigation Screen needs to work nicely with the Navigation block (and vice versa), much of the current effort from contributors here is focused on the Navigation Block. With this in mind, current efforts include:
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:
Add content-width option to GS & theme.jsonJSONJSON, 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.
The Query Block MVPMinimum Viable Product"A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia is ready! Next up, work will start to polish the experience with a focus on suggesting Patterns in block placeholder states.
Lots of CSSCSSCascading Style Sheets. improvements, such as adding missing classes to the Home item and active item, among others, as well as a CSS refactor.
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.
Block & PluginPluginA 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
With the upcoming release of WordPress 5.7 right around the corner, please don’t forget to check the most recent dev-notes to keep updated on the latest APIAPIAn 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. changes.
Performance matters, and as such there have been recent improvements to frontend loading times, enabled by default in Full Site Editing but opt-in in non-FSE templates for backward compatibility.
Contributors
As suggested during the recent Hallway Hangout hosted by @bernhard-reiter focused on writing end-to-end tests, contributors are encouraged to file issues requesting end-to-end tests when spotting a regressionregressionA 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. with the “[Package] E2E Tests” label.
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.
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 triagetriageThe 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 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.
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor weekly Wednesdays @ 14:00 UTC in #core-editor focused on all-things Gutenberg.
Block-Based Themes meeting twice monthly on Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.