Title: 2021 – Page 39 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:04 pm _on_ May 3, 2021 Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [developer-documentation ( 8 )](https://make.wordpress.org/core/tag/developer-documentation/), [devhub ( 2 )](https://make.wordpress.org/core/tag/devhub/), [docs ( 11 )](https://make.wordpress.org/core/tag/docs/), [documentation ( 4 )](https://make.wordpress.org/core/tag/documentation/), helphub # 󠀁[Docs Focus role & workflow during WordPress release cycle](https://make.wordpress.org/core/2021/05/03/docs-focus-role-workflow-during-wordpress-release-cycle/)󠁿 This is a summary of a discussion which happened during previous Docs Team meetings and also a proposal for WordPress 5.8. During the previous weekly Docs team meetings, a discussion started about how the [Documentation team](https://make.wordpress.org/docs) could be better involved during WordPress release cycles. In recent years, all new versions of WordPress have had a person responsible for the “Docs” focus ([@justinahinon](https://profiles.wordpress.org/justinahinon/) for 5.3 and 5.5, [@audrasjb](https://profiles.wordpress.org/audrasjb/) for 5.4 and 5.7, [@sncoker](https://profiles.wordpress.org/sncoker/), [@m_butcher](https://profiles.wordpress.org/m_butcher/) and their cohort for 5.6). But even if all the 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 the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/). The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. (which are the main tasks of the Docs Focus) are published, the Docs team pointed out that it’s difficult for them to make sure all the end-user documentation (HelpHub) and the developer documentation( DevHub) are up to date after a new version is released. ## WordPress release Docs Focus [@milana_cap](https://profiles.wordpress.org/milana_cap/) ([@zzap](https://profiles.wordpress.org/zzap/) on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)) is the [Docs Focus Lead for WordPress 5.8](https://make.wordpress.org/core/5-8/). The role of Docs Focus lead includes the responsibilities listed below. For each responsibility, one or more deputies will help the release Docs Focus lead but Milana Cap will remain the unique Docs reference person for the Release squad. ### Developers notes wrangling on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. * Keep track of changes within the release that require dev notes (changes that require a dev notedev 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. must be labelled with the `needs-dev-note` workflow keyword) * Ensure all dev notes are written with enough time to proofread, reviewed, and published prior to the field guide (which is published by the Docs Focus lead at the same time as 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)](https://make.wordpress.org/core/2021/page/39/?output_format=md#alpha-beta). 1) * Coordinate with the participants of those tickets with the best understanding of the changes (the committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., component maintainers, the contributor who owns the ticketticket Created for both bug reports and feature development on the bug tracker.) to draft dev notes * If a ticket participant is not available to write a dev note, finding someone to write one, or writing one yourself * Proofread and review dev notes as they are available from the Documentation Wrangling team - Verify code examples - Make suggestions for additional examples - Ensure the developer notes accurately and thoroughly describe the problem, solution, and identify proper usage of the changes ### End-user documentation wrangling on HelpHub * Keep track of changes within the release that require changes on HelpHub (changes that require HelpHub changes (whether it’s a new page or just an update on existing ones) must be labelled with the `needs-codex` workflow keyword) * Ensure any documentation pages required for new features are created before the release * Ensure any existing documentation page for changes on existing features are ready to be updated (the day of the final release) * Write and publish the release version page on HelpHub * Update WordPress versions page on the Codex ### Developer documentation wrangling on DevHub * Keep track of changes within the release that require changes on DevHub (changes that require DevHub changes –whether it’s a new page or just an update on existing ones– must be labelled with the `needs-docs` workflow keyword) * Ensure any documentation sections required for new features are ready to be updated( they are updated a few days **after** the final release, once the DevHub automatic parser has synchronized the documentation) - “More information” sections on DevHub ([example](https://developer.wordpress.org/reference/classes/wp_query/#more-information)) - BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor Developer Docs * Ensure any existing documentation sections for changes on existing features are ready to be updated (they are also updated a few days **after** the final release) - “More information” sections on DevHub * - Block editor Developer Docs ## Workflow A new spreadsheet will be created by the docs focus lead. The previous spreadsheet was built for dev notes over all, with a simple “HelpHub” column. For WordPress 5.8, the Docs team proposed to use a tab for each responsibility: Dev notes, HelpHub and DevHub, so they can be equally wrangled. Also, Core changes from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. will be separated from Block Editor changes from 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 by the repository owner. [https://github.com/](https://github.com/). _Reviewed by [@milana\_cap](https://profiles.wordpress.org/milana_cap/) and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/)._ [#5-8](https://make.wordpress.org/core/tag/5-8/), [#developer-documentation](https://make.wordpress.org/core/tag/developer-documentation/), [#devhub](https://make.wordpress.org/core/tag/devhub/), [#docs](https://make.wordpress.org/core/tag/docs/), [#documentation](https://make.wordpress.org/core/tag/documentation/), [#helphub](https://make.wordpress.org/core/tag/helphub/) [ ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/) 8:00 pm _on_ May 3, 2021 Tags: [github ( 9 )](https://make.wordpress.org/core/tag/github/) # 󠀁[Expired GitHub and WordPress.org profile connections](https://make.wordpress.org/core/2021/05/03/expired-github-and-wordpress-org-profile-connections/)󠁿 A little over one year ago, a [feature was rolled out allowing a GitHub account to be connected to a WordPress.org account](https://make.wordpress.org/core/2020/03/19/associating-github-accounts-with-wordpress-org-profiles/). > In recent releases, the process of collecting props for non-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/](https://wordpress.org/) contributions (namely 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/](https://wordpress.org/gutenberg/)) > has been highly manual and error prone, occasionally resulting in contributors > not receiving proper credit. Connecting your WordPress.org and 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 by the repository owner. [https://github.com/](https://github.com/) > accounts will allow automatic tooling to be built which reduces the burden on > release teams to maintain a credit list. When access is revoked for the “WordPress.org Profiles” application for a GitHub account, this is respected and the WordPress.org and GitHub profiles are unlinked. However, GitHub also expires application connections automatically that have not been used in over a year. Because WordPress.org respects all access changes for this application, it has resulted in some profiles becoming unlinked. **If you had previously connected your accounts, please check that your connection is still valid.** To check, visit your WordPress.org profile ([https://profiles.wordpress.org/me/](https://profiles.wordpress.org/me/)) and verify that your GitHub account is still listed. If you do not see a GitHub account listed, your connection has expired, been revoked, or one was never made. [⌊A screenshot of a WordPress.org profile with the GitHub field outlined.⌉⌊A screenshot of a WordPress.org profile with the GitHub field outlined.⌉[ Going forward, WordPress.org will now check that linked profiles are still up to date, haven’t been deleted, or suspended by GitHub more regularly regularly, and as a result the application connection will not go stale. _Props to [@dd32](https://profiles.wordpress.org/dd32/) for investigating and fixing the issue, [@cbringmann](https://profiles.wordpress.org/cbringmann/) for proofreading._ [#github](https://make.wordpress.org/core/tag/github/) [ ](https://profiles.wordpress.org/jorgefilipecosta/) [Jorge Costa](https://profiles.wordpress.org/jorgefilipecosta/) 7:04 pm _on_ May 3, 2021 Tags: [block-editor ( 140 )](https://make.wordpress.org/core/tag/block-editor/), [chats ( 25 )](https://make.wordpress.org/core/tag/chats/), [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/) # 󠀁[Editor chat summary: Wednesday, 28 April 2021](https://make.wordpress.org/core/2021/05/03/editor-chat-summary-wednesday-28-april-2021/)󠁿 This post summarizes the weekly _editor chat _meeting on [Wednesday, 28 April 2021, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210428T1400) held in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1619618454408600). ## 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/](https://wordpress.org/gutenberg/)󠁿 10.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)](https://make.wordpress.org/core/2021/page/39/?output_format=md#alpha-beta)󠁿. release. The first topic was the Gutenberg 10.5 release. The RC was already shipped a week before the chat [https://github.com/WordPress/gutenberg/releases/tag/v10.5.0-rc.1](https://github.com/WordPress/gutenberg/releases/tag/v10.5.0-rc.1). [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) said that we had some PR’s that were cherry-picked since the RC. The final release was scheduled for the day of the chat. [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) gave public congratulations to [@ajitbohra](https://wordpress.slack.com/team/U2JCYPN0L) for the first RC release! ## Posts requiring feedback and insights. [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) said that we have two important posts published recently that deserve wide attention: * [Full Site Editing Go/No Go: Next steps](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/). Sharing important details about the next steps for Full Site Editing global styles and the WordPress 5.8 release. * [IE 11 support phase out plan](https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/). Sharing a plan to remove IE11 support form WordPress. In case anyone has some insights or thoughts to share please leave a comment on the posts! Your insights are appreciated! ## ⏎ Monthly Plan and key project updates. ### Global Styles **Shipped this week** 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. * clean-ups [#31224](https://github.com/WordPress/gutenberg/pull/31224) block.json / 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. supports * duotone [#26752](https://github.com/WordPress/gutenberg/pull/26752) * padding: fix to allow units other than px [#31057](https://github.com/WordPress/gutenberg/pull/31057) * font-size: can be used in nodes other than the wrapper [#30879](https://github.com/WordPress/gutenberg/pull/30879) * border-color: fix for dynamic blocks [#31020](https://github.com/WordPress/gutenberg/pull/31020) * blocks - padding for site title [#31125](https://github.com/WordPress/gutenberg/pull/31125) - padding and letter casing for site tagline [#31042](https://github.com/WordPress/gutenberg/pull/31042) - link color for post date [#30791](https://github.com/WordPress/gutenberg/pull/30791) - table uses now background/text colors from the theme [#30791](https://github.com/WordPress/gutenberg/pull/30791) Internationalization * custom templates can be translated via theme.json [#29828](https://github.com/WordPress/gutenberg/pull/29828) KSES * fix to sanitizing user styles [#30888](https://github.com/WordPress/gutenberg/pull/30888) Site editor: * fixes for preset classes in the site editor [#31218](https://github.com/WordPress/gutenberg/pull/31218) [#31217](https://github.com/WordPress/gutenberg/pull/31217) [#31204](https://github.com/WordPress/gutenberg/pull/31204) * fix for color selector in the UIUI User interface color panel [#31015](https://github.com/WordPress/gutenberg/pull/31015) **Ongoing** theme.json * Changes to format [#29891](https://github.com/WordPress/gutenberg/issues/29891) are ready [#30541](https://github.com/WordPress/gutenberg/pull/30541) we’re now testing and polishing. It also includes versioning (aka migrate the older formats to the new one). * Improve 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 take data from the theme directly [#31267](https://github.com/WordPress/gutenberg/pull/31267) block.json / block supports * typography (line-height, font-weight, etc) can be used in nodes other than the wrapper [#30880](https://github.com/WordPress/gutenberg/pull/30880) * border and color (background, text) to the pull quote block [#30951](https://github.com/WordPress/gutenberg/pull/30951) New style properties * Add support for letter-spacing [#31118](https://github.com/WordPress/gutenberg/pull/31118) **Misc** * Add a new endpoint that exposes block editor settings through 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/](https://developer.wordpress.org/rest-api/)( by mobile to access global styles data) [#29969](https://github.com/WordPress/gutenberg/pull/29969) * standardize capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). of wp_template, wp_template_part and wp_global_styles [#30893](https://github.com/WordPress/gutenberg/pull/30893) **Priorities** The priority continues to be shipping [#29891](https://github.com/WordPress/gutenberg/issues/29891) as soon as possible to unblock related work. [#28913](https://github.com/WordPress/gutenberg/issues/28913) is a good issue to look at if you can lend a hand (help with reviews, migrate more blocks, more properties, etc). ### Block 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. and Navigation Editor. [@andraganescu](https://profiles.wordpress.org/andraganescu/) provided the following update: > The legacy widget got an UXUX User experience upgrade and now the default view > is the preview while the embedded widget editor 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. had a performance > overhaul. The focus on back combat continued with more testing with legacy widgets > from various plugins. As expected a lot of new issues were opened. > On navigation editor the steady pace of improvements continued last week. Many > thanks for the many welcome contributions! ### Navigation block. [@joen](https://profiles.wordpress.org/joen/) provided the following update: > For the navigation block, we recently merged a padding change and I’m doing some > followups ([submenu gap](https://github.com/WordPress/gutenberg/pull/31195), [placeholder items](https://github.com/WordPress/gutenberg/pull/31275), > [nav screen](https://github.com/WordPress/gutenberg/pull/31228)). Also looking > at [small separate improvements](https://github.com/WordPress/gutenberg/pull/31198), > and hope to get back to patterns now that the padding change is merged  — thank > you for reviews. ### Full Site Editing/Page templates [@youknowriad](https://profiles.wordpress.org/youknowriad/) provided the following update regarding page templates: > I’ve spent some time iterating on that on the last days. We now merged the UIs > for templates under a single “template” panel in the 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., we iterated a bit on the design > of the “frame” to distinguish properly between template and post modes and simplified > the save flow a bit. There are a number of iterations we could make, I don’t expect > all of them to happen before 5.8, at some point, we’d make a final decision about > whether it’s good enough to include. [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) made a heads up regarding the query block: > `Query` block has now a `wrapper element` which for now is `div` (and will be > the default when more tags will be supported) here: [https://github.com/WordPress/gutenberg/pull/30804](https://github.com/WordPress/gutenberg/pull/30804) > I’ve added a deprecation so everything will work as before but it will be good > to update any block themes you have that use `Query`. ## Task Coordination ### 󠀁[@aristath](https://profiles.wordpress.org/aristath/)󠁿 This past week: * Continued working on PR to autogenerate anchors for headings – [#30825](https://github.com/WordPress/gutenberg/pull/30825) * Continued on [@nosolosw](https://wordpress.slack.com/team/U49EF0UH4)‘s existing PR to allow inner blocks in quotes – [#25892](https://github.com/WordPress/gutenberg/pull/25892) * Sustainability: PR to split `theme.css` styles and only load the ones for rendered blocks – [#31239](https://github.com/WordPress/gutenberg/pull/31239) * Smaller PRs, mostly to improve code quality & linting errors * Lots and lots of PR reviews Next week: Continue working on all the things mentioned above ### 󠀁[@mamaduka](https://profiles.wordpress.org/mamaduka/)󠁿 Helping out with the new Navigation Editor screen: * Sync menu [name updates](https://github.com/WordPress/gutenberg/pull/31093). * Introduce useMenuEntityProp [hook](https://github.com/WordPress/gutenberg/pull/31132). * Better handling of unsaved changes. PRs [one](https://github.com/WordPress/gutenberg/pull/31119) and [two](https://github.com/WordPress/gutenberg/pull/31197). Continued my work on the “Most Used Terms” feature and got great feedback about improvements. Thanks, everyone.Planning to continue working on Navigation Editor tasks. ### 󠀁[@paaljoachim](https://profiles.wordpress.org/paaljoachim/)󠁿 * PR for tags. [https://github.com/WordPress/gutenberg/pull/30598](https://github.com/WordPress/gutenberg/pull/30598) * “Move post/page title to the top bar” issue. [https://github.com/WordPress/gutenberg/issues/27093](https://github.com/WordPress/gutenberg/issues/27093)( Which we need to talk closer about during the Open Floor.) * Working on various design issues and triages. * VVV/Vagrat documentation updates. ### 󠀁[@ntsekouras](https://profiles.wordpress.org/ntsekouras/)󠁿 * Add wrapper and align support in Query block([https://github.com/WordPress/gutenberg/pull/30804](https://github.com/WordPress/gutenberg/pull/30804)) * Suggesting block patterns in block placeholder states([https://github.com/WordPress/gutenberg/pull/29602](https://github.com/WordPress/gutenberg/pull/29602)) * Extract Heading Level Control Component ([https://github.com/WordPress/gutenberg/pull/31045](https://github.com/WordPress/gutenberg/pull/31045))– needs review ### 󠀁[@annezazu](https://profiles.wordpress.org/annezazu/)󠁿 Continued FSE Program work with the [fifth call for testing](https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/), [publishing a schedule of upcoming plans](https://make.wordpress.org/test/2021/04/22/upcoming-fse-outreach-program-schedule/), reviewing/adding to a brief FSE doc, and[ launched a second round of questions](https://make.wordpress.org/test/2021/04/28/fse-program-bring-your-questions-round-two/). I’m planning to likely do a [hallway hangout ](https://make.wordpress.org/test/2021/04/08/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-8-april/) tomorrow on FSE issues/prs/designs in [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00) for anyone interested! ### 󠀁[@poena](https://profiles.wordpress.org/poena/)󠁿 Plans to continue on the site block changes but also I want to test the theme.json format and update the tutorial for creating block themes. Awaiting review of the letter-spacing. ### 󠀁[@vdwijngaert](https://profiles.wordpress.org/vdwijngaert/)󠁿 Will be working on a PR for moving the post/page title to the top bar. Current PR: [#31240](https://github.com/WordPress/gutenberg/pull/31240), but going to close that in favor of a new one based on a 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". ### 󠀁[@jffng](https://profiles.wordpress.org/jffng/)󠁿 * fix a [template loading bug for child themes](https://github.com/WordPress/gutenberg/pull/31123) * add a filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/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. to [determine whether a theme can use the site editor](https://github.com/WordPress/gutenberg/pull/31235) * optionally [render a classic nav source using the nav block](https://github.com/WordPress/gutenberg/pull/30852) ### 󠀁[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)󠁿 The main goal for next week is to review [https://github.com/WordPress/gutenberg/pull/30541](https://github.com/WordPress/gutenberg/pull/30541) and help it be merged. Plans on reviewing other Global Styles PR that are opened( e.g: [https://github.com/WordPress/gutenberg/pull/30880](https://github.com/WordPress/gutenberg/pull/30880)). Wants to fix [https://github.com/WordPress/gutenberg/issues/27478](https://github.com/WordPress/gutenberg/issues/27478), which is probably very simple but may have a considerable impact and should be done ASAP. ## Open floor ### Post title moving in site editor [@bobbingwide](https://profiles.wordpress.org/bobbingwide/) said that there’s a problem moving the post title in the Site Editor. Adding that it’s tricky editing the topmost block if one does not have the toolbar set to top. [@joen](https://profiles.wordpress.org/joen/) said [@ellatrix](https://profiles.wordpress.org/ellatrix/) is working on a fix https:// github.com/WordPress/gutenberg/pull/31134. ### G2 Components [@aristath](https://profiles.wordpress.org/aristath/) asked the status of “G2 components” and if there is any plan on removing them. [@youknowriad](https://profiles.wordpress.org/youknowriad/) said that G2 is not removed but while reviewing some of the integration PRs, he noticed that G2 reimplements a lot of things we already have in Gutenberg in its own way. So the plan is still to integrate it but aligning with Gutenberg practices. [#block-editor](https://make.wordpress.org/core/tag/block-editor/), [#chats](https://make.wordpress.org/core/tag/chats/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 4:34 pm _on_ May 3, 2021 Tags: [auto-updates ( 13 )](https://make.wordpress.org/core/tag/auto-updates/), core-auto-update, [updater ( 21 )](https://make.wordpress.org/core/tag/updater/) # 󠀁[[Feature project] Updates on updating the updaters](https://make.wordpress.org/core/2021/05/03/feature-project-updates-on-updating-the-updaters/)󠁿 _Sorry, I couldn’t help myself…_ In November 2020, I posted about an initiative to [update the updaters](https://make.wordpress.org/core/2020/11/27/update-the-updater/). It took a bit longer than expected to research the issue and an efficient way to manage the project, but here we are. ## Context The WordPress updaters are a set of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher classes that assures that users can safely upgrade WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., plugins, themes, and translations. The ability to manually update WordPress from the adminadmin (and super admin) area, and to install and update plugins and themes, has existed since 2.3 in 2007. Auto- update features were added in WordPress 3.7 (for minor releases), extended in 5.5( as opt-in for plugins and themes), and 5.6 (major releases). To make the user experience of auto-updates even better, and build trust with users and extenders, it’s important that this mechanism works well and provides all the failsafe checks needed. The WordPress Core update has proven to be generally reliable, but it doesn’t actually have many tests nor is well documented. There are also some reliability concerns around adding new files and the overall number of changed files, which is the reason WordPress currently tries to [keep the number of changed files in minor releases to a minimum](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-minor-versions/). Plugins and themes updaters are older: in general, all of them can be improved. ## 󠀁[󠀁[Goal The project goal is to review the existing state of the updaters and propose ways to improve them. * [WordPress](https://developer.wordpress.org/reference/classes/wp_upgrader/) * [Core](https://developer.wordpress.org/reference/classes/core_upgrader/) * [Plugins](https://developer.wordpress.org/reference/classes/plugin_upgrader/) * [Themes](https://developer.wordpress.org/reference/classes/theme_upgrader/) ## 󠀁[󠀁[Outcomes The expected outcomes are: 1. Make sure the zips upload and unpacking are safe. 2. Create a mechanism to upgrade and rollback. 3. Have managed updates (database migrations). 4. Create a unified 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. convention for requirements and dependencies. ### 󠀁[󠀁[Outcome 1 – Make sure the zip uploads and unpacking are safe With the introduction of auto-updates, these processes run more frequently.. So relatively small issues get triggered more often, and with that become a bigger problem. They also now more often run unattended: an auto-update that breaks could lead to quite problematic results. The goal here is to address most of the known issues related to: * downloading and extracting update packages * copying files and directories * improving documentation for updates * adding some automated tests * making the update process more reliable in general #### Related TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets **Edited** [2021-05-06T19:38 MDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210507T0138): added [#36710](https://core.trac.wordpress.org/ticket/36710) and [#36373](https://core.trac.wordpress.org/ticket/36373) to the list of tickets. [@pbiron](https://profiles.wordpress.org/pbiron/). * [#14781 Allow upload of PHP files as plugin](https://core.trac.wordpress.org/ticket/14781) * [#15134 WordPress should not try to remove theme’s or plugin’s directory recursively if the directory is a symlink](https://core.trac.wordpress.org/ticket/15134) * [#17301 Keep the connection open when doing upgrades or long-running operations](https://core.trac.wordpress.org/ticket/17301) * [#20944 Changing plugin filename causes Fatal error on automatic activation after update](https://core.trac.wordpress.org/ticket/20944) * [#26626 WP_Upgrader::unpack_package() can overflow path name length limits](https://core.trac.wordpress.org/ticket/26626) * [#29408 Symlinked themes and plugins should not be updatable](https://core.trac.wordpress.org/ticket/29408) * [#33571 Improvements for plugin upgrades when disk space runs out (or other write failure)](https://core.trac.wordpress.org/ticket/33571) * [#34676 Optimize bulk plugin updates](https://core.trac.wordpress.org/ticket/34676) * [#35217 WP_Upgrader: writes temporary directory name to plugin folder if zip doesn’t have directory](https://core.trac.wordpress.org/ticket/35217) * [#36373 Plugin update fails silently when using zipfile without subdirectory](https://core.trac.wordpress.org/ticket/36373) * [#38084 Fix Inconsistency Theme and Plugin Update Process When No Package Found](https://core.trac.wordpress.org/ticket/38084) * [#44002 fread(): Length parameter must be greater than 0 – Happens on all updates to core, plugins, themes](https://core.trac.wordpress.org/ticket/44002) * [#44118 WordPress performs some unnecessary plugin update checks](https://core.trac.wordpress.org/ticket/44118) * [#44418 fs_unavailable while auto-updating plugins](https://core.trac.wordpress.org/ticket/44418) * [#50349 Plugin Update deletes plugin and showing “could not delete old plugin” message](https://core.trac.wordpress.org/ticket/50349) * [#50849 Incorrect action passed to hooks when updating plugin/theme by uploading ZIP file](https://core.trac.wordpress.org/ticket/50849) * [#51823 Native auto updater caused plugin update to fail and disappears plugin from directory](https://core.trac.wordpress.org/ticket/51823)( Should be fixed with [Rollback Update Failure](https://wordpress.org/plugins/rollback-update-failure) 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.) * [#52342 Update copy_dir and _copy_dir for $dirlist error reporting](https://core.trac.wordpress.org/ticket/52342)( this is fixed, but worth revisiting in case if it has dependencies with the other bugs) * [#36710 Symlinked directories should not be deleted recursively](https://core.trac.wordpress.org/ticket/36710) * [#36373 Plugin update fails silently when using zipfile without subdirectory](https://core.trac.wordpress.org/ticket/36373) ### 󠀁[󠀁[Outcome 2 – Create a mechanism to upgrade and rollback. When a core auto-update fails, core has long had the ability to automatically attempt a “rollback” to the latest stable release (in the 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". that the site is running). Note: for core auto-updates, “rollback” is not attempted for certain failures (e. g. “disk full”, etc). This capabilitycapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). should be extended to be available for plugin and theme updates. Work on some of these issues is already undergoing as part the [rollback update feature](https://wordpress.org/plugins/rollback-update-failure). #### Related Trac tickets * [#37301 A way to test plugin/theme installs and updates before applying](https://core.trac.wordpress.org/ticket/37301) * [#49963 Security of failed update/rollback](https://core.trac.wordpress.org/ticket/49963) * [#50937 Auto-backup in core](https://core.trac.wordpress.org/ticket/50937) * [#51816 Implement auto recovery mode during auto update cron](https://core.trac.wordpress.org/ticket/51816) * [#51857 Add rollback for failed plugin/theme updates](https://core.trac.wordpress.org/ticket/51857) * [#51928 Provide plugin/theme update failure data to dot org](https://core.trac.wordpress.org/ticket/51928) ### 󠀁[󠀁[Outcome 3 – Have managed updates (database migrations) Plugins should be able to easily run database migrations, so that update and rollback could be performed not only for files but also for data. Yoast already does this by having a migrations library: * [https://github.com/Yoast/wordpress-seo/tree/trunk/lib/migrations](https://github.com/Yoast/wordpress-seo/tree/trunk/lib/migrations) * [https://github.com/Yoast/wordpress-seo/tree/trunk/src/config/migrations](https://github.com/Yoast/wordpress-seo/tree/trunk/src/config/migrations) If we had a unified process for data migrations in core, WordPress would be able to run the latest available migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. after an update or rollback: * without the need to store anything about the previous state * without requiring anything from the plugin author, apart from adding a “migrations” folder #### Relevant Trac tickets * [#32606 Plugin data migration](https://core.trac.wordpress.org/ticket/32606) * [#36887 Database upgrades should fail gracefully](https://core.trac.wordpress.org/ticket/36887) * [#49188 Add a check for tables structures](https://core.trac.wordpress.org/ticket/49188) ### Outcome 4 – Create a unified JSON convention for requirements and dependencies. Different plugins have introduced compatibility tags (For example, [Elementor](https://developers.elementor.com/compatibility-tag/) and [WooCommerce](https://docs.woocommerce.com/document/create-a-plugin/#section-10)). In the long run, this could become harder to manage. #### Relevant Trac tickets * [#11308 Handling plugin dependencies](https://core.trac.wordpress.org/ticket/11308) * [#20241 make it possible for plugins to activate other plugins](https://core.trac.wordpress.org/ticket/20241) * [#22316 Plugin Dependencies (Yet Another Plugin Dependencies Ticket)](https://core.trac.wordpress.org/ticket/22316) * [#23912 Add Composer package description](https://core.trac.wordpress.org/ticket/23912) * [#47285 Better Management of External Asset Dependencies](https://core.trac.wordpress.org/ticket/47285) * [#52154 Ability to install site with predefined configuration without Docker or console commands — analogue of package.json for full site installation with exact settings, plugins, themes and their settings](https://core.trac.wordpress.org/ticket/52154) [@afragen](https://profiles.wordpress.org/afragen/) has written a lightweight library, [wp-dependency-installer](https://github.com/afragen/wp-dependency-installer), that takes a JSON config file and can install a suggested or required plugin dependency. He mentions this as a lighter-weight solution to something like the TGMPA library. This makes it possible to solve many of the issues above. ## How to contribute 1. Familiarize yourself with the existing classes, listed above. 2. Update your local WordPress [SVN](https://make.wordpress.org/core/handbook/tutorials/installing-wordpress-locally/from-svn/#5-updating-your-subversion-install)( use `svn up`) or [Git repo](https://github.com/wordpress/wordpress-develop) (use` git pull`) to the latest version of WordPress trunktrunk A 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.. 3. Pick a ticketticket Created for both bug reports and feature development on the bug tracker. from the above list, review its history, refresh it if needed or make a new 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.. 4. [Upload your patch](https://make.wordpress.org/core/handbook/working-with-trac/opening-a-ticket/#attach-files) to the Trac ticket you created, and add the keywords `has-patch` and `needs-testing` 5. If during the exploration of the above goals you can think of other enhancements, please create a [new ticket](https://core.trac.wordpress.org/newticket) and assign it to the [Update/Install component](https://make.wordpress.org/core/components/upgrade-install/) ## Keeping Discussions Focused Any discussion about the specifics of a patch itself should happen on Trac. Any discussion about the broader scope of what this feature project is about should take place during the weekly chat in the [#core-auto-update](https://make.wordpress.org/core/tag/core-auto-update/) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). ## What’s next? See you on [May 4, 2021 at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210504T1700) for the kickoff meeting, during the weekly [#core-auto-update](https://make.wordpress.org/core/tag/core-auto-update/). In the meantime, if you already know that you want to work on a specific goal or a specific ticket, please leave a comment. Thank you! _Thanks [@afragen](https://profiles.wordpress.org/afragen/), [@audrasjb](https://profiles.wordpress.org/audrasjb/), and [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) for the peer review_. _Thanks [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) for combing through Trac to look for the tickets!_ [#auto-updates](https://make.wordpress.org/core/tag/auto-updates/), [#updater](https://make.wordpress.org/core/tag/updater/) [ ](https://profiles.wordpress.org/itsjusteileen/) [Eileen Violini](https://profiles.wordpress.org/itsjusteileen/) 3:15 pm _on_ May 3, 2021   # 󠀁[Core Editor Meeting Agenda 5 May 2021](https://make.wordpress.org/core/2021/05/03/core-editor-meeting-agenda-5-may-2021/)󠁿 Facilitator: @get_dave This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, May 5, 2021, 02:00PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210505T1400). _This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._ * [Gutenberg 10.5.3](https://github.com/WordPress/gutenberg/releases) * 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/](https://wordpress.org/gutenberg/) 10.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)](https://make.wordpress.org/core/2021/page/39/?output_format=md#alpha-beta). * [WordPress 5.8](https://make.wordpress.org/core/5-8/) * [What’s New in Gutenberg](https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/) * [Full Site Editing Upcoming Schedule](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/) * Key project updates: - Global Styles * - 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 - Navigation block - Full Site Editing * Task Coordination * Open Floor If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion: * If you have anything to share for the Task Coordination section, please leave it as a comment on this post. * If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below. [ ](https://profiles.wordpress.org/meher/) [Meher Bala](https://profiles.wordpress.org/meher/) 8:01 am _on_ May 3, 2021 Tags: 5-8-release-leads, [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/), [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/), [FSE ( 5 )](https://make.wordpress.org/core/tag/fse/), [fse-outreach-experiment ( 14 )](https://make.wordpress.org/core/tag/fse-outreach-experiment/), [jQuery ( 15 )](https://make.wordpress.org/core/tag/jquery/)    # 󠀁[DevChat meeting Summary – April 28, 2021](https://make.wordpress.org/core/2021/05/03/devchat-meeting-summary-april-28-2021/)󠁿 [Agenda](https://make.wordpress.org/core/2021/04/28/dev-chat-agenda-for-april-28-2021/) for the two meetings. Thanks to [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) for leading the 05:00 and 20:00 UTC devchats respectively. [Link to 05:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1619586070258000) [Link to 20:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1619640124378200) ## **Announcements and news** * [Latest Trac statistics, code commits, and associated props for last week](https://make.wordpress.org/core/2021/04/26/a-week-in-core-april-26-2021/) from [@audrasjb](https://profiles.wordpress.org/audrasjb/) * [Overview of the Gutenberg process of refining the block toolbar to make it more intuitive and predictable to use](https://make.wordpress.org/core/2021/04/23/core-editor-improvement-refining-the-block-toolbar/) from [@annezazu](https://profiles.wordpress.org/annezazu/) * [Outlining the Internet Explorer 11 Support Phase Out Plan](https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/) from [@desrosj](https://profiles.wordpress.org/desrosj/)  * [Outlining the FSE Outreach Program Schedule noting the timing of upcoming Gutenberg releases and the related FSE Calls for Testing](https://make.wordpress.org/test/2021/04/22/upcoming-fse-outreach-program-schedule/) posted by [@annezazu](https://profiles.wordpress.org/annezazu/) [More on FSE in its section below] * [What FSE means for site owners and operators, agencies and theme/plugin developers, and contributors and volunteers ?](https://wordpress.org/news/2021/04/curious-about-full-site-editing/) posted by [@chanthaboune](https://profiles.wordpress.org/chanthaboune/)  * [What’s next in Gutenberg?](https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/) ## **Feedback on posts requested** * [@iandunn](https://profiles.wordpress.org/iandunn/) needs your input on the topic of assisting 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. developers to avoid specific bugs that result in WordPress end users having a bad experience. He has suggested potential solutions including static code analysisStatic code analysis "...the analysis of computer software that is performed without actually executing programs, in contrast with dynamic analysis, which is analysis performed on programs while they are executing." - [Wikipedia](https://en.wikipedia.org/wiki/Static_program_analysis), and has provided a list of questions to help guide the discussion. [Do read it](https://make.wordpress.org/meta/2021/04/27/automatically-catching-bugs-in-plugins/) and provide feedback from your perspective. * [@francina](https://profiles.wordpress.org/francina/): Would Stats Dashboards Help Your Team? [Read this post](https://make.wordpress.org/updates/2021/02/26/would-stats-dashboards-help-your-team/) for more details. Would folks in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. feel that any sorts of stats on a dashboard would support in their work in core? * New team [CC Search to join WordPress](https://ma.tt/2021/04/cc-search-to-join-wordpress-org/). CC Search, a CC0 (Creative Commons Zero) image search engine, is joining the WordPress project with more than 500 million openly licensed and public domain images discoverable from more than 50 sources, audio and video soon to come. [Read this post for more information](https://ma.tt/2021/04/cc-search-to-join-wordpress-org/) [@chanthaboune](https://profiles.wordpress.org/chanthaboune/): more news and context coming in the next few weeks. * Wonderful design reference for those looking for ways to quickly prototype WordPress UIUI User interface in Figma. [Read this blog post](https://wordpress.org/news/2021/04/getting-started-with-the-figma-wordpress-design-library/). * WP Briefing podcast. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/): these are super quick to digest, provide a good on-ramp to what’s latest in WordPress. Check out [all the episodes at this link](https://wordpress.org/news/podcast/) and find links to subscribe in your favorite podcast app. ## **WordPress 5.8 Release** [@francina](https://profiles.wordpress.org/francina/) gave an update – Thanks to everyone who volunteered and right now I can confirm these roles: **Release leadRelease Lead The community member ultimately responsible for the Release.:** Matt Mullenweg ([@matt](https://profiles.wordpress.org/matt/)) **Release Coordinators:** Jeff Paul ([@jeffpaul](https://profiles.wordpress.org/jeffpaul/)) and Jonathan Desrosiers( [@desrosj](https://profiles.wordpress.org/desrosj/))**Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead:** Luke Carbis ([@lukecarbis](https://profiles.wordpress.org/lukecarbis/))** Core Tech Lead:** Helen Hou-Sandí ([@helen](https://profiles.wordpress.org/helen/))** Editor Tech Lead:** Riad Benguella ([@youknowriad](https://profiles.wordpress.org/youknowriad/))** Marketing and Communication Lead:** Josepha Haden-Chomphosy ([@chanthaboune](https://profiles.wordpress.org/chanthaboune/))** Documentation Lead:** Milana Cap ([@milana_cap](https://profiles.wordpress.org/milana_cap/))** Support Lead:** Mary Job ([@mariaojob](https://profiles.wordpress.org/mariaojob/))** Testing Lead:** Piotrek Boniu ([@boniu91](https://profiles.wordpress.org/boniu91/)) * [@francina](https://profiles.wordpress.org/francina/): “If I have messaged you and asked to join the release as part of the supporting crew, thanks for being part of the collaborative work that makes WordPress so great. Everyone! Join us in the channel [#5-8-release-leads](https://make.wordpress.org/core/tag/5-8-release-leads/)“ * If you have any questions about releases which you are following along, and if you want to ask questions:[ #core](https://wordpress.slack.com/archives/C02RQBWTW) and [#core-editor](https://make.wordpress.org/core/tag/core-editor/) are the right channels * [5.8 release team](https://make.wordpress.org/core/5-8/) ## **Full Site Editing (FSE) related items** * [Open call to send in your questions on Full Site Editing (FSE) Round 2](https://make.wordpress.org/test/2021/04/28/fse-program-bring-your-questions-round-two/)– reminder from[ @annezazu](https://profiles.wordpress.org/annezazu/) that you can submit questions, no matter who you are. The call closes 12 May 2021. This is part of the collaboration in[ #fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00) * [More posts on FSE in the posts requesting feedback section above] * Marketing has social media text available which can be reused to promote the different FSE calls  * [@helen](https://profiles.wordpress.org/helen/) making a 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 theme with the full site editor ## **Component maintainers and committers update** * [@sergey](https://profiles.wordpress.org/sergey/): Work has continued on further fixing some long-standing coding standards issues in core, see ticketticket Created for both bug reports and feature development on the bug tracker. [#52627](https://core.trac.wordpress.org/ticket/52627) for more details.Build/Test Tools, Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/39/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week. * [@clorith](https://profiles.wordpress.org/clorith/): Site Health catching up a bit on older and unanswered tickets * [@audrasjb](https://profiles.wordpress.org/audrasjb/): Menus, Widgets, Upgrade/ Install: nothing new. I scrubbed some tickets in the Menus component but no major news to share. * Following on from discussion last week [@marybaum](https://profiles.wordpress.org/marybaum/) nominates [@abhanonstopnewsuk](https://profiles.wordpress.org/abhanonstopnewsuk/) as co-maintainer for the [Help/ About page component](https://make.wordpress.org/core/components/help-about/) * In the last week, they have been going through the tickets since and will give an update in future devchats. ## **jQuery** * [@Hareesh](https://profiles.wordpress.org/hareesh/): some attention requested on [#52163](https://core.trac.wordpress.org/ticket/52163). With this out of the way, we would have less jQuery migrate warnings, and it would be easier to fix any remaining warnings. * [@clorith](https://profiles.wordpress.org/clorith/): jQuery UI hasn’t been updated yet, we are still waiting on their release, which I believe is scheduled for the end of May/start of June  * [@davidb](https://profiles.wordpress.org/davidb/): jQuery release is right before 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 then, if the dates hold * [@clorith](https://profiles.wordpress.org/clorith/): Yeah, which is a bit tighter than I’d like, but it is what it is… we’ll have a look once it’s ready to see what’s going on and what the best approach is. Building from source while they’re still modifying it isn’t really an option in my opinion. ## **Open Floor** * [@notlaura](https://profiles.wordpress.org/notlaura/): feedback requested on ticket [#53070](https://core.trac.wordpress.org/ticket/53070). Establish a Core CSSCSS Cascading Style Sheets. deprecation path, and ask if anyone is interested in working on it! This is something we’ve been discussing in [#core-css](https://make.wordpress.org/core/tag/core-css/) ## **Community** * [@chanthaboune](https://profiles.wordpress.org/chanthaboune/): As you may be aware, many of our fellow contributors are experiencing disruptions in their lives right now above and beyond the (seemingly) routine disruptions of this pandemic life. From big earthquakes to big spikes in COVID cases to unrest right outside their doors, some of your WordPress pals are hurting more than usual. * For my part, I can say take whatever time you need to take care of yourselves. You are important and WordPress is not more important than your health and well- being. * For all of us, if you haven’t reached out to your friends to see how they are, please do. Thanks to [@meher](https://profiles.wordpress.org/meher/) and [@webcommsat](https://profiles.wordpress.org/webcommsat/) for the devchat notes and [@marybaum](https://profiles.wordpress.org/marybaum/) for her help with them. [#5-8](https://make.wordpress.org/core/tag/5-8/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#fse](https://make.wordpress.org/core/tag/fse/), [#fse-outreach-experiment](https://make.wordpress.org/core/tag/fse-outreach-experiment/), [#jquery](https://make.wordpress.org/core/tag/jquery/) [ ](https://profiles.wordpress.org/ryokuhi/) [Stefano Minoia](https://profiles.wordpress.org/ryokuhi/) 5:24 pm _on_ April 30, 2021 Tags: [make.wordpress.org/accessibility ( 13 )](https://make.wordpress.org/core/tag/make-wordpress-org-accessibility/), [p2-xpost ( 213 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Proposal: new workflow keyword to exclude tickets until review is needed](https://make.wordpress.org/core/2021/04/30/xpost-proposal-new-workflow-keyword-to-exclude-tickets-until-review-is-needed/)󠁿 X-comment from [+make.wordpress.org/accessibility](https://make.wordpress.org/accessibility/): Comment on [Proposal: new workflow keyword to exclude tickets until review is needed](https://make.wordpress.org/accessibility/2021/04/29/proposal-new-workflow-keyword-to-exclude-tickets-until-review-is-needed/#comment-73103) [ ](https://profiles.wordpress.org/ajitbohra/) [Ajit Bohra](https://profiles.wordpress.org/ajitbohra/) 12:22 am _on_ April 30, 2021 Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 217 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s New In Gutenberg 10.5? (28 April)](https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/)󠁿 Two weeks have passed since 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/](https://wordpress.org/gutenberg/) release, which means a new version is already available! Gutenberg 10.5 introduces many new blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. patterns, embedded PDFs, enhancements to the Template Editing Mode, improvements to Widgets 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., and many 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 as well. ## New block patterns and pattern transformations Gutenberg 10.5 puts the focus on bringing several new block patterns, [revisiting the bundled block patterns](https://github.com/WordPress/gutenberg/pull/29973) as well as [adding more opinionated Query Block ones](https://github.com/WordPress/gutenberg/pull/30763). It also [enables block pattern transformations](https://github.com/WordPress/gutenberg/pull/30469) that are contextual to the currently selected simple block, without inner blocks. ## Enhancements to the Template Editing Mode With the goal of editing templates with blocks, a “Template Editing Mode” was introduced in recent Gutenberg versions so that users can edit a template directly from the post editor, switching between post and template editing. This release provides several flow and interface enhancements to this feature, including the possibility to [create custom block templates in classic themes](https://github.com/WordPress/gutenberg/pull/30438). Other improvements include [unifying the saving flow](https://github.com/WordPress/gutenberg/pull/30793) between Template Mode and Default Mode, [moving the Template Mode _Edit_ and _New_ links ](https://github.com/WordPress/gutenberg/pull/30900) to a dedicated new panel, and [replacing the _Document_ tab with a _Template_ tab](https://github.com/WordPress/gutenberg/pull/30860) in Template Mode. ## Embedded PDFs with File Block The File Block now supports embedding PDFs in most major browsers. This option can be enabled or disabled through a 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. toggle. ## Improvements to Widgets in the Customizer While Gutenberg 10.4 enabled Block Widgets in the Customizer, this new iteration enhances the experience by enabling [upload capabilities for media](https://github.com/WordPress/gutenberg/pull/30954) and [Richtext formats](https://github.com/WordPress/gutenberg/pull/30952). ## No more auto-scrolling when selecting blocks Before 10.5, when any block that was slightly out of view was selected, the page would automatically scroll so that the top of the selected block was visible, potentially disorienting the user. From 10.5 onwards, the scroll will only happen if the block is not selected directly by the user. # 10.5 ### Enhancements * **Buttons** **Block**: - Add Typography support. ([30394](https://github.com/WordPress/gutenberg/pull/30394)) - Explicitly add text-align-center to legacy buttons. ([30525](https://github.com/WordPress/gutenberg/pull/30525)) - Update to use color support utils to retrieve classes and styles. ([30870](https://github.com/WordPress/gutenberg/pull/30870)) * **Columns** **Block**: Add column count to the column block label. ([30248](https://github.com/WordPress/gutenberg/pull/30248)) * **File Block**: Add support for embedding PDFs. ([30857](https://github.com/WordPress/gutenberg/pull/30857)) * **List** **Block**: Add placeholder attribute. ([30958](https://github.com/WordPress/gutenberg/pull/30958)) * **Post** **Comments Link** **Block**: New block added. ([29564](https://github.com/WordPress/gutenberg/pull/29564)) * **Site Logo** **Block**: - Update the site logo description to be more illustrative. ([30909](https://github.com/WordPress/gutenberg/pull/30909)) - Add a default width value. ([30907](https://github.com/WordPress/gutenberg/pull/30907)) * **Site Title** **Block**: - Normalize the toolbar. ([30999](https://github.com/WordPress/gutenberg/pull/30999)) - Normalize the toolbar (II). ([31032](https://github.com/WordPress/gutenberg/pull/31032)) * **Social Links** **Block**: - Add text placeholder next to the appender. ([29851](https://github.com/WordPress/gutenberg/pull/29851)) - Remove obsolete hardcoded focus style from Social Links. ([30721](https://github.com/WordPress/gutenberg/pull/30721)) * **Template Part** **Block**: Add active block variation information in Block Parent Selector. ([30731](https://github.com/WordPress/gutenberg/pull/30731)) * **Term Description** **Block**: Don’t output if there’s no description. ([30564](https://github.com/WordPress/gutenberg/pull/30564)) * **Verse** **Block**: Add support for custom colors. ([27736](https://github.com/WordPress/gutenberg/pull/27736)) * **Video** **Block**: Add uploading state. ([30837](https://github.com/WordPress/gutenberg/pull/30837)) * **Block Patterns:** - Revisit the bundled block patterns. ([29973](https://github.com/WordPress/gutenberg/pull/29973)) - Suggest block pattern transformations that are contextual to the currently selected ‘simple’ blocks (no InnerBlocks). ([30469](https://github.com/WordPress/gutenberg/pull/30469)) - Small adjustments to bundled block patterns. ([31105](https://github.com/WordPress/gutenberg/pull/31105)) - Query Patterns: * Try more opinionated query block patterns. ([30763](https://github.com/WordPress/gutenberg/pull/30763)) * Add the small image and title pattern back in, fix excerptExcerpt An 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. length..( [30817](https://github.com/WordPress/gutenberg/pull/30817)) * **Components**: Add create-styles. (30509) * **Design Tools:** - Add border color, style, and width support. ([30124](https://github.com/WordPress/gutenberg/pull/30124)) - BoxControl: Allow configurable sides. ([30606](https://github.com/WordPress/gutenberg/pull/30606)) - Color Block Support: Add utilities to retrieve color classes and styles. ( [30869](https://github.com/WordPress/gutenberg/pull/30869)) * **General Interface:** - Animate the canvas transitions. ([30802](https://github.com/WordPress/gutenberg/pull/30802)) - Include block title into block switcher label. ([30808](https://github.com/WordPress/gutenberg/pull/30808)) - Inspector Controls: Rephrase, polish, and make consistent color labels. ([30075](https://github.com/WordPress/gutenberg/pull/30075)) * - Update design of the resize handles. ([30339](https://github.com/WordPress/gutenberg/pull/30339)) - Icons: Update icons for text overlay and crop. ([30673](https://github.com/WordPress/gutenberg/pull/30673)) * **i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/39/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.**: Add `resetLocaleData` method. ([30419](https://github.com/WordPress/gutenberg/pull/30419)) * **Publishing Flow**: Show post events in the post schedule calendar. ([29716](https://github.com/WordPress/gutenberg/pull/29716)) * **Template Editing Mode**: - Allow creating custom block templates in classic themes. ([30438](https://github.com/WordPress/gutenberg/pull/30438)) - Move the template mode edit and new links to a dedicated template panel. ( [30900](https://github.com/WordPress/gutenberg/pull/30900)) - Replace the document tab with a template tab in template mode. ([30860](https://github.com/WordPress/gutenberg/pull/30860)) - Unify saving flow between template mode and default mode. ([30793](https://github.com/WordPress/gutenberg/pull/30793)) - Update the template mode canvas padding and adds a backlinkBacklink Incoming links to a web page. Search engines view backlinks as a reputation builder. The more quality (as determined by the search engine) incoming backlinks a site has usually helps a site to rank better in search engine results.. ([30658](https://github.com/WordPress/gutenberg/pull/30658)) * **Site Editor**: - Add ‘area’ selection to convert to template part flow. ([30395](https://github.com/WordPress/gutenberg/pull/30395)) - Add do_block_template_part function. ([30345](https://github.com/WordPress/gutenberg/pull/30345)) - Add skip link to block templates. ([30336](https://github.com/WordPress/gutenberg/pull/30336)) - Remove single-post from the default templates set. ([29668](https://github.com/WordPress/gutenberg/pull/29668)) - Themes: Fix template-hierarchy fallbacks. ([30599](https://github.com/WordPress/gutenberg/pull/30599)) * **Writing Flow**: Scroll selected block only if it has no focus. ([30924](https://github.com/WordPress/gutenberg/pull/30924)) ### Bug Fixes * Apply a StyleProvider around fills that can be used inside the 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.. ([31073](https://github.com/WordPress/gutenberg/pull/31073)) * **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**: Make preloaded OPTIONS requests use `parse` setting. ( [28862](https://github.com/WordPress/gutenberg/pull/28862)) * **Block Library**: - Duplicate media types to avoid bad imports. ([30973](https://github.com/WordPress/gutenberg/pull/30973)) - **Image Block:** Disable media buttons in the uploading state. ([30863](https://github.com/WordPress/gutenberg/pull/30863)) - **Query:** Fix max-height to query pattern preview. ([30757](https://github.com/WordPress/gutenberg/pull/30757)) - **Post Title:** Fix warnings for RichText in inline containers. ([30666](https://github.com/WordPress/gutenberg/pull/30666)) - **Site Title:** Add default block after pressing enter at the end of Site Title. ([30996](https://github.com/WordPress/gutenberg/pull/30996)) * **Block Editor**: - Bring back imageDefaultSize shim for WP 5.7. ([30955](https://github.com/WordPress/gutenberg/pull/30955)) - Fix the position of vertical add a new block in RTL mode. ([31035](https://github.com/WordPress/gutenberg/pull/31035)) - Template part: Fix PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher notice for placeholder block. ([30928](https://github.com/WordPress/gutenberg/pull/30928)) * **Components:** - Add a StyleProvider to support CSSCSS Cascading Style Sheets.-in-JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. components inside iframes. ([31010](https://github.com/WordPress/gutenberg/pull/31010)) - Fix “RadioControl: checked” style outside of Gutenberg. ([30670](https://github.com/WordPress/gutenberg/pull/30670)) - Fix Post Date component. ([30790](https://github.com/WordPress/gutenberg/pull/30790)) - Fix Post Publishing Popover moving when certain dates are clicked. ([30298](https://github.com/WordPress/gutenberg/pull/30298)) - Fix useForceUpdate Memory Leak: Only setState if the component is still mounted.( [30667](https://github.com/WordPress/gutenberg/pull/30667)) * **General Interface:** Fix is-link style to take colors from wp-adminadmin (and super admin) theme. ([30823](https://github.com/WordPress/gutenberg/pull/30823)) * **Inserter: **Stop event propagation for the select element’s onBlur to fix the behavior in iOSiOS The operating system used on iPhones and iPads. when selecting a pattern categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging..( [30717](https://github.com/WordPress/gutenberg/pull/30717)) * **Site Editor:** - Focus save button when entities save states panel is opened. ([30873](https://github.com/WordPress/gutenberg/pull/30873)) - Remove call to wpautop that unintentionally alters block markup in template parts. ([30552](https://github.com/WordPress/gutenberg/pull/30552)) * **Template Editing Mode:** Hide the template selector and template mode from non-viewable post types. ([30861](https://github.com/WordPress/gutenberg/pull/30861)) ### Experiments * **Block-based Widgets:** - **API:** * Don’t use deprecated widget_class property. ([30429](https://github.com/WordPress/gutenberg/pull/30429)) * Fix null instance property when instance settings are empty. ([30713](https://github.com/WordPress/gutenberg/pull/30713)) * Remove deprecated properties. ([30853](https://github.com/WordPress/gutenberg/pull/30853)) - **Customizer Integration:** * Add media uploader capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). to block- 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. customize screen. ([30954](https://github.com/WordPress/gutenberg/pull/30954)) * Add move to widget area dropdown in customizer. ([30896](https://github.com/WordPress/gutenberg/pull/30896)) * Add rich text formats. ([30952](https://github.com/WordPress/gutenberg/pull/30952)) * Fix editing performance in Widgets Customizer. ([30654](https://github.com/WordPress/gutenberg/pull/30654)) * Fix block-based widget customizer initializing too soon. ([30864](https://github.com/WordPress/gutenberg/pull/30864)) * Refactor the inspector in Widgets Customizer to use coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. controls. ([30431](https://github.com/WordPress/gutenberg/pull/30431)) - **Legacy Widget:** Improve backward compatibility. ([30709](https://github.com/WordPress/gutenberg/pull/30709)) - **Widget editor:** * Add a toolbar button to move between widget areas. ([30826](https://github.com/WordPress/gutenberg/pull/30826)) * Fix the undo/redo buttons in the standalone block-based widgets editor.( [30989](https://github.com/WordPress/gutenberg/pull/30989)) * **Navigation Editor and Block:** - Fix navigation placeholder height issue. ([30824](https://github.com/WordPress/gutenberg/pull/30824)) - Fix alignment issue on the nav screen manage locations buttons. ([30441](https://github.com/WordPress/gutenberg/pull/30441)) - Limit navigation nesting depth to 5. ([30199](https://github.com/WordPress/gutenberg/pull/30199)) - Nav-created drafts should not render on the frontend. ([29692](https://github.com/WordPress/gutenberg/pull/29692)) - Page List: Add ability to convert to navigation links. ([30390](https://github.com/WordPress/gutenberg/pull/30390)) - Show justification controls for vertical variant. ([30351](https://github.com/WordPress/gutenberg/pull/30351)) - Use theme locations description instead of the slug for navigation screen location labels. ([30797](https://github.com/WordPress/gutenberg/pull/30797)) * **Global Styles:** - Absorb editor settings transformation in WP_Theme_JSON. ([30610](https://github.com/WordPress/gutenberg/pull/30610)) - Clean cached data when switching themes. ([30830](https://github.com/WordPress/gutenberg/pull/30830)) - Extract sanitize method. ([30809](https://github.com/WordPress/gutenberg/pull/30809)) - Fix: CSS variable reference mechanism regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2021/page/39/?output_format=md#blocker). 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.. ([31015](https://github.com/WordPress/gutenberg/pull/31015)) - Make the dependency of the star matcher explicit when translating `theme.json`.( [30604](https://github.com/WordPress/gutenberg/pull/30604)) - Only remove the default font family in the editor from themes with `theme. json` file. ([30895](https://github.com/WordPress/gutenberg/pull/30895)) - Refactor how we iterate over the tree. ([30801](https://github.com/WordPress/gutenberg/pull/30801)) - Remove no longer needed translations handled in PHP for settings. ([30605](https://github.com/WordPress/gutenberg/pull/30605)) - 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.: Add util to transform from a v0 schema to the latest. ([30600](https://github.com/WordPress/gutenberg/pull/30600)) ### Documentation * **docgen:** - Add support for TS exported static non-function variables. ([30971](https://github.com/WordPress/gutenberg/pull/30971)) - Add support for assignment patterns. ([30681](https://github.com/WordPress/gutenberg/pull/30681)) - Add support for object-destructuring. ([30675](https://github.com/WordPress/gutenberg/pull/30675)) - Find parameters by index rather than name and handle array destructuring. ( [29945](https://github.com/WordPress/gutenberg/pull/29945)) * **Handbook:** - Add documentation for border block supports. ([31039](https://github.com/WordPress/gutenberg/pull/31039)) - Add documentation for border styles. ([31040](https://github.com/WordPress/gutenberg/pull/31040)) - Add fix to suggested prefixes of the 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"..( [30953](https://github.com/WordPress/gutenberg/pull/30953)) - Change references from Block Style Variations to Block Styles. ([30911](https://github.com/WordPress/gutenberg/pull/30911)) - Fix Block Editor 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) link. ([30569](https://github.com/WordPress/gutenberg/pull/30569)) - Fix more examples for register_block_type – apiVersion to api_version. ([30819](https://github.com/WordPress/gutenberg/pull/30819)) - Fix PHP example for register_block_type – apiVersion to api_version. ([30818](https://github.com/WordPress/gutenberg/pull/30818)) - Fixed a type and made the whole explanation more clear. ([30487](https://github.com/WordPress/gutenberg/pull/30487)) - Fixes broken 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 by the repository owner. [https://github.com/](https://github.com/) links to commonly used labels. ([30875](https://github.com/WordPress/gutenberg/pull/30875)) - Improve semantics in the block-based theme guide. ([30946](https://github.com/WordPress/gutenberg/pull/30946)) - Include a note about `is_default` property for `register_block_style`. ([30792](https://github.com/WordPress/gutenberg/pull/30792)) - Organize Block API Reference. ([30980](https://github.com/WordPress/gutenberg/pull/30980)) - Packages: Further clarify the npm publishing process. ([30733](https://github.com/WordPress/gutenberg/pull/30733)) - Update getting started with code. ([30447](https://github.com/WordPress/gutenberg/pull/30447)) * **Libs:** - Blocks: Fix PHPDocs of `gutenberg_block_has_support`. ([31050](https://github.com/WordPress/gutenberg/pull/31050)) - Query Utils: Fix return type of `construct_wp_query_args()`. ([30611](https://github.com/WordPress/gutenberg/pull/30611)) * **License:** Interim dual license of future contributions. ([30383](https://github.com/WordPress/gutenberg/pull/30383)) * **Packages:** - Block Library – Social Links: Update param type. ([30652](https://github.com/WordPress/gutenberg/pull/30652)) - Components: Add documentation for the text prop on the Button component. ( [30796](https://github.com/WordPress/gutenberg/pull/30796)) - Core Data: Fixes return type for getEntitiesByKind. ([30639](https://github.com/WordPress/gutenberg/pull/30639)) - Block Editor: Update import statement of ImageSizeControl component. ([30704](https://github.com/WordPress/gutenberg/pull/30704)) - HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.: Add namespace param clarification. ([30501](https://github.com/WordPress/gutenberg/pull/30501)) ### Code Quality * **Block Editor:** - Simplify focus capture. ([31036](https://github.com/WordPress/gutenberg/pull/31036)) - Standardize loading default block editor settings. ([30245](https://github.com/WordPress/gutenberg/pull/30245)) * **Block Library:** - Button Block: Use hook-based border support. ([30194](https://github.com/WordPress/gutenberg/pull/30194)) - Cover: Rename isBlogUrl to `isUploadingMedia`. ([30435](https://github.com/WordPress/gutenberg/pull/30435)) - Cover: Use ALLOWED_MEDIA_TYPES shared constant. ([30977](https://github.com/WordPress/gutenberg/pull/30977)) * **Block Patterns:** Clean up bundled pattern titles & categories. ([30998](https://github.com/WordPress/gutenberg/pull/30998)) * **Components:** Remove `create-styles` in favor of vanilla emotion. ([31048](https://github.com/WordPress/gutenberg/pull/31048)) * **dom:** - Add types to caret placement functions. ([30750](https://github.com/WordPress/gutenberg/pull/30750)) - Add types to document-has-selection. ([30386](https://github.com/WordPress/gutenberg/pull/30386)) - Add types to is-edge and dependencies. ([30546](https://github.com/WordPress/gutenberg/pull/30546)) - Add types to miscellaneous files. ([30774](https://github.com/WordPress/gutenberg/pull/30774)) - Add types to removeInvalidHTML and stripHTML. ([30752](https://github.com/WordPress/gutenberg/pull/30752)) - Only assert defined in development. ([30807](https://github.com/WordPress/gutenberg/pull/30807)) - Type the remaining files. ([30841](https://github.com/WordPress/gutenberg/pull/30841)) * **Drop zone:** Rewrite without provider. ([30310](https://github.com/WordPress/gutenberg/pull/30310)) * **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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.:** - Account for editor styles file removal on WP trunktrunk A 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.. ( [30894](https://github.com/WordPress/gutenberg/pull/30894)) - Format all markdown files using Prettier formatter. ([30715](https://github.com/WordPress/gutenberg/pull/30715)) - Format all JSON files using Prettier formatter. ([30714](https://github.com/WordPress/gutenberg/pull/30714)) - Updated `.editorconfig` files to work with automatic file formatting. ([30794](https://github.com/WordPress/gutenberg/pull/30794)) - Update WP compatibility check in `gutenberg_pre_init()`. ([29938](https://github.com/WordPress/gutenberg/pull/29938)) * Improve get_merged_data() code. ([30612](https://github.com/WordPress/gutenberg/pull/30612)) * Remove unnecessary semicolons in PHP. ([30780](https://github.com/WordPress/gutenberg/pull/30780)) * Replace older-style PHP type conversion functions with typecasts. ([30531](https://github.com/WordPress/gutenberg/pull/30531)) ### Tools * **Testing:** - **Cover Block:** * Add edit media integration tests. ([30270](https://github.com/WordPress/gutenberg/pull/30270)) * Replace media end-to-end test. ([30306](https://github.com/WordPress/gutenberg/pull/30306)) - Fix end-to-end test failure screenshots not capturing at the right time. ( [28449](https://github.com/WordPress/gutenberg/pull/28449)) - Fixture regeneration: Infer tabs use from the prettier configuration. ([30813](https://github.com/WordPress/gutenberg/pull/30813)) - Skip unstable template part end-to-end test. ([30748](https://github.com/WordPress/gutenberg/pull/30748)) - Trim block fixture HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. when generating other test fixture files. ([30981](https://github.com/WordPress/gutenberg/pull/30981)) - Wire PHP tests for block editor settings. ([30984](https://github.com/WordPress/gutenberg/pull/30984)) * **wp-env:** - Better errors when Docker is not started. ([30882](https://github.com/WordPress/gutenberg/pull/30882)) - Bump tt1-blocks dependency to v0.4.5. ([30045](https://github.com/WordPress/gutenberg/pull/30045)) - Disable Xdebug for PHP < 7.2. ([30651](https://github.com/WordPress/gutenberg/pull/30651)) - Fix chown cannot access ‘wp-config.php’. ([30053](https://github.com/WordPress/gutenberg/pull/30053)) - Fix issue with unquoted paths in the docker-compose call. ([3069](https://github.com/WordPress/gutenberg/pull/30692) [2)](https://github.com/WordPress/gutenberg/pull/30692) - [Remove platform-specific destroy commands. (30638)](https://github.com/WordPress/gutenberg/pull/30692) - Set default environment type to local. ([28808](https://github.com/WordPress/gutenberg/pull/28808)) - Update changelog and CI. ([30646](https://github.com/WordPress/gutenberg/pull/30646)) * **Build Tooling:** - Add comments to the webpack entry point function. ([30629](https://github.com/WordPress/gutenberg/pull/30629)) - Create frontend entry points for block-library, outputting code loadable from the browser. ([30341](https://github.com/WordPress/gutenberg/pull/30341)) - Perf Workflow: Trigger upon release publishing. ([30628](https://github.com/WordPress/gutenberg/pull/30628)) - Pull trunk before pushing. ([30615](https://github.com/WordPress/gutenberg/pull/30615)) - Remind about required cherry-picks after npm publishing. ([30868](https://github.com/WordPress/gutenberg/pull/30868)) - Update development tools to work with PostCSS (try 2). ([30347](https://github.com/WordPress/gutenberg/pull/30347)) - Use consistently the latest keyword for npm publishing. ([30866](https://github.com/WordPress/gutenberg/pull/30866)) * **Scripts:** - Allow CSS modules in the build commands. ([29182](https://github.com/WordPress/gutenberg/pull/29182)) - Include YAML files in prettification. ([30240](https://github.com/WordPress/gutenberg/pull/30240)) ## **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.5 | 7.86s | 55.86ms | | Gutenberg 10.4 | 7.25s | 42.51ms | | WordPress 5.7 | 6.86s | 37.1ms | Kudos to all the contributors that helped with the release! 👏 _Thanks @youknowriad and [@priethor](https://profiles.wordpress.org/priethor/) for helping with the release and the release post, respectively._ [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) [ ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/) 2:14 pm _on_ April 29, 2021 Tags: [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)    # 󠀁[CSS Chat Agenda: April 29, 2021](https://make.wordpress.org/core/2021/04/29/css-chat-agenda-april-29-2021/)󠁿 This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for [Thursday, April 29, at 5:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+CSS+Core+Chat&iso=20210429T17&p1=418&ah=1). This meeting will be held in the [#core-css](https://make.wordpress.org/core/tag/core-css/) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). If there’s any topic you’d like to discuss, or if you have suggestions for discussion questions, please leave a comment below! * Housekeeping - Volunteer needed to lead 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. scrub next week * Project Updates - CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582)) - Color Scheming ([#49999](https://core.trac.wordpress.org/ticket/49999)) - CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS deprecation path ([#53070](https://core.trac.wordpress.org/ticket/53070)) * Open Floor + CSS Link Share [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-css](https://make.wordpress.org/core/tag/core-css/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 3:42 pm _on_ April 28, 2021 Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[CSS Chat Summary: 22 April 2021](https://make.wordpress.org/core/2021/04/28/css-chat-summary-22-april-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1619125546431200). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## Project updates ### CSSCSS Cascading Style Sheets. Audit (󠀁[#49582](https://core.trac.wordpress.org/ticket/49582)󠁿) * [@notlaura](https://profiles.wordpress.org/notlaura/) has started [a document for the Make post about the project](https://docs.google.com/document/d/1NfVg-8IWHhUfKPQKToIW13XBGO4uVHZ3nhKgoh6Ba6Y/edit?usp=sharing). Once the Make post is done we can update the ticketticket Created for both bug reports and feature development on the bug tracker. * [@ryelle](https://profiles.wordpress.org/ryelle/) is very close to getting the repo into the WordPress org 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 by the repository owner. [https://github.com/](https://github.com/)_[ SPOILER ALERT]_ [this has now happened!](https://github.com/WordPress/css-audit) ### Color Scheming (󠀁[#49999](https://core.trac.wordpress.org/ticket/49999)󠁿) * [@ryelle](https://profiles.wordpress.org/ryelle/) shared [a branch she started in order to continue exploring custom property names](https://github.com/WordPress/wordpress-develop/compare/master%E2%80%A6ryelle:try/custom-properties), which has further developed her `[prefix]--[location]--[property]--[state]` pattern: - The `[property]` part no longer has to map exactly to a specific CSS property. This will avoid duplicate definitions & also allow some flexibility to make the names easier to understand - The `[location]` part is partly based on class names, and partly on her experience talking to designers * Documentation of the naming decision process, and the custom property names themselves, will be essential. We could also provide stylelint rules and possibly an allowlist of all the possible names * Closing the discussion, a decision was made that [@ryelle](https://profiles.wordpress.org/ryelle/)’ s approach is the one we will follow * The next step is to write up & discuss the naming documentation, and decide how to roll out the custom properties e.g. component by component * [@ryelle](https://profiles.wordpress.org/ryelle/) also has a make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post coming soon about the project ### CSS deprecation path * @tellthemachines [has opened a ticket for this](https://core.trac.wordpress.org/ticket/53070) which she plans to mention in the next dev chat ## Open floor / CSS link share * @tellthemachines shared [an update that Firefox has made to `outline` which now follows `border-radius`](https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/88#css) * [@notlaura](https://profiles.wordpress.org/notlaura/) shared her pen [The Beauty of FizzBuzz](https://codepen.io/laras126/pen/dyNQMdq), using `nth-child` to solve FizzBuzz with CSS and also make fun patterns Thanks everyone! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/40/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/38/?output_format=md)