Title: 2021 – Page 35 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 7:09 pm _on_ May 20, 2021 Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-improvement ( 35 )](https://make.wordpress.org/core/tag/core-editor-improvement/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/)    # 󠀁[Core Editor Improvement: Contextual patterns for easier creation](https://make.wordpress.org/core/2021/05/20/core-editor-improvement-contextual-patterns-for-easier-creation/)󠁿 We’ve all been there. Staring at a blank page sometimes with an idea of what you want to create and sometimes with a mind as blank as the page. To make the creation process easier and to leap into the [pattern filled future](https://make.wordpress.org/design/2021/05/12/wordpress-org-patterns-directory-i2/), work is underway to suggest 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 based on the block one is working with. Tied to this, when using the block inserter, block patterns will be suggested where possible. In the long run as this work continues and spreads to more blocks, it will be easier to create content and get inspired without leaving the editor.  **Exploring integrated patterns** For now with 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.2, you can see how this flow works with a few blocks including the Heading Block, Query Block, Social Icon Block, Buttons Block, and Paragraph Block. In particular, [lots of work has been done around the Query Block](https://github.com/WordPress/gutenberg/pull/28891) to make it easier to create beautiful layouts in a few clicks with this powerful block. Here’s a quick visual showing this experience with the Quote Block:  _Video showing how the block patterns can be found in the transforms options_ You can begin to explore these patterns in three ways: * Browse through them in the Patterns tab of the Block Inserter. * Select directly from the Quick Inserter.  * Navigate to them in the transform menu of individual blocks.  **Integrate your custom block patterns** On the flip side, if you’re creating your own custom block patterns, there’s a new experimental `blockTypes` property being worked on that will allow your patterns to show up in the transform menu. [Here’s an example ](https://github.com/WordPress/gutenberg/blob/848949d057bce0374f04e33d1dfbeab209eef7aa/lib/block-patterns.php#L176) of how this works currently. This is still in the early stages though as it’s utilizing experimental components and might need changes down the road so stay tuned! If you do try this out and run into any bugs/feature requests, [feel free to share them in the Gutenberg repo](https://github.com/WordPress/gutenberg/issues/). **Help with these efforts** Expect this work to continue expanding both in terms of integrating patterns in intuitive places and in terms of the number of unique patterns. To get a sense of where this work is headed in the future, [check out this early PR](https://github.com/WordPress/gutenberg/pull/29890). If you’re interested in helping in this area, make sure to join [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7), check out the [current focuses](https://make.wordpress.org/core/tag/gutenberg-next/), and attend the [Core Editor weekly meeting Wednesday @ 14:00 UTC](https://make.wordpress.org/core/tag/core-editor-agenda/). Finally, if you’re wanting to dive into custom block patterns, [check out the Learn WordPress course](https://learn.wordpress.org/workshop/registering-block-patterns/) along [with the documentation](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-patterns/) to get started.  [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-improvement](https://make.wordpress.org/core/tag/core-editor-improvement/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) [ ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/) 5:50 pm _on_ May 20, 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: May 20, 2021](https://make.wordpress.org/core/2021/05/20/css-chat-agenda-may-20-2021/)󠁿 This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for [Thursday, May 20, at 5:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+CSS+Core+Chat&iso=20210520T17&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, please leave a comment below! * Housekeeping * Project Updates - Color Scheming ([#49999](https://core.trac.wordpress.org/ticket/49999)) * Discuss next steps - 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)) - CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582)) * 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/) 2:44 pm _on_ May 20, 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: 13 May 2021](https://make.wordpress.org/core/2021/05/20/css-chat-summary-13-may-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1620940031160000). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## Project updates ### Color Scheming (󠀁[#49999](https://core.trac.wordpress.org/ticket/49999)󠁿) * [@ryelle](https://profiles.wordpress.org/ryelle/) has posted [an update on the project on Make](https://wp.me/p2AvED-n8d) and shared it in the dev chats * [@melchoyce](https://profiles.wordpress.org/melchoyce/) dropped in to share a link to [the Figma file used for the mockups in the Make post](https://www.figma.com/file/9gqAxMGXMZtNDlO3Wgh6N2/Dark-Mode?node-id=0%3A1) * Next steps will be discussed in the next meeting ### CSSCSS Cascading Style Sheets. Deprecation Path (󠀁[#53070](https://core.trac.wordpress.org/ticket/53070)󠁿) * @tellthemachines is planning to write a Make post about the project to clarify details of the proposed methodology ### CSS Audit (󠀁[#49582](https://core.trac.wordpress.org/ticket/49582)󠁿) * The automated report generation PR needs 1 review – UPDATE: the PR has now been merged ## Open floor / CSS link share * [@notlaura](https://profiles.wordpress.org/notlaura/) mentioned two CSS related tickets: - [Move title to header toolbar](https://github.com/WordPress/gutenberg/pull/31288) in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) - [Combine/globalize the CSS/JS between Site Health & Privacy Settings](https://core.trac.wordpress.org/ticket/52429) in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. * We discussed the second issue ([#52429](https://core.trac.wordpress.org/ticket/52429)) and decided on a suitable approach * [@notlaura](https://profiles.wordpress.org/notlaura/) assigned herself to implement it * [@notlaura](https://profiles.wordpress.org/notlaura/) shared a [W3C CSSWG draft](https://github.com/w3c/csswg-drafts/issues/3559) relating to issues caused by `@supports`, for example browsers that support ` gap` but only in the context of `grid`, not `flexbox` Thanks everyone! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/javiercasares/) [Javier Casares](https://profiles.wordpress.org/javiercasares/) 5:38 am _on_ May 20, 2021 Tags: [make.wordpress.org/hosting ( 7 )](https://make.wordpress.org/core/tag/make-wordpress-org-hosting/), [p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Why hosters should install the PHP-intl extension](https://make.wordpress.org/core/2021/05/20/xpost-why-hosters-should-install-the-php-intl-extension/)󠁿 X-post from [+make.wordpress.org/hosting](https://make.wordpress.org/hosting/): [Why hosters should install the PHP-intl extension](https://make.wordpress.org/hosting/2021/05/20/why-hosters-should-install-the-php-intl-extension/) [ ](https://profiles.wordpress.org/joedolson/) [Joe Dolson](https://profiles.wordpress.org/joedolson/) 7:51 pm _on_ May 19, 2021 Tags: [make.wordpress.org/accessibility ( 12 )](https://make.wordpress.org/core/tag/make-wordpress-org-accessibility/), [p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Follow-up Workflow Keyword Proposal](https://make.wordpress.org/core/2021/05/19/xpost-follow-up-workflow-keyword-proposal/)󠁿 X-comment from [+make.wordpress.org/accessibility](https://make.wordpress.org/accessibility/): Comment on [Follow-up Workflow Keyword Proposal](https://make.wordpress.org/accessibility/2021/05/19/follow-up-workflow-keyword-proposal/#comment-73112) [ ](https://profiles.wordpress.org/joedolson/) [Joe Dolson](https://profiles.wordpress.org/joedolson/) 7:27 pm _on_ May 19, 2021 Tags: [make.wordpress.org/accessibility ( 12 )](https://make.wordpress.org/core/tag/make-wordpress-org-accessibility/), [p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: +make.wordpress.org/core/](https://make.wordpress.org/core/2021/05/19/xpost-make-wordpress-org-core/)󠁿 X-post from [+make.wordpress.org/accessibility](https://make.wordpress.org/accessibility/): [+make.wordpress.org/core/](https://make.wordpress.org/accessibility/2021/05/19/make-wordpress-org-core/) [ ](https://profiles.wordpress.org/mattchowning/) [Matt Chowning](https://profiles.wordpress.org/mattchowning/) 6:04 pm _on_ May 19, 2021   # 󠀁[Apologies on Gutenberg Dual-Licensing Process](https://make.wordpress.org/core/2021/05/19/apologies-on-gutenberg-dual-licensing-process/)󠁿 Earlier this week two issues were opened in the 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/) repo to help begin the process of obtaining consent from contributors to relicense their work under the GPLv2 and MPLv2 licenses.  I appreciate everyone’s quick responses on both of those issues, but understand that both raised some concerns that I would like to address here.  The first is a concern with the amount of notifications from the [contributor agreement issue](https://github.com/WordPress/gutenberg/issues/31893) and the second is a concern with emails listed in the [confirming commit authors issue](https://github.com/WordPress/gutenberg/issues/31913). Apologies to anyone negatively impacted by either of those issues as that was certainly not the intent. There was consideration for alternate routes of gathering consent such as Google Forms, Google Sheets, a markdown file in the repo, and a standalone website but none offered the transparency and simplicity as a 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/) issue.  While prior Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. posts on the [proposal](https://make.wordpress.org/core/2020/09/21/proposal-dual-licensing-gutenberg-under-gpl-v2-0-and-mpl-v2-0/) and [next steps](https://make.wordpress.org/core/2021/03/05/dual-licensing-gutenberg-next-steps/) for dual-licensing Gutenberg did mention the planned use of GitHub issues to gather consent from contributors, those posts could have been more descriptive in their plans.  In aiming for transparency and simplicity there were unintended side effects of adding noise into your daily lives with the GitHub notifications.  I apologize for this negative impact to you and any other unintended consequences. There was also consideration for directly emailing or 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/) direct messaging to gain confirmation on potentially unknown commit authors, but these options were dismissed in favor of a GitHub issue to allow for transparency and simplicity in the process.  In sharing emails from the publicly available Gutenberg repo’s [`git log`](https://git-scm.com/docs/git-log) there were concerns that this opened those people up for spam and other unsolicited emails.  While those email addresses were already publicly available, I recognize that we made them more readily accessible and apologize for any negative impact this has on those individuals as a side effect of our attempt to transparently handle the process of confirming commit authors. Again, it is worth repeating that I appreciate everyone’s quick responses on these issues and I apologize for anyone negatively impacted by them.  If you have any additional questions or concerns, please utilize the comments on this post and I will work to ensure they are addressed. **_Props to [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) for drafting and reviewing this post._** [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 1:39 pm _on_ May 19, 2021 Tags: [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/), [updater ( 21 )](https://make.wordpress.org/core/tag/updater/), [upgrade-install ( 32 )](https://make.wordpress.org/core/tag/upgrade-install/) # 󠀁[Upgrade/Install component meeting notes from May 18th, 2021](https://make.wordpress.org/core/2021/05/19/upgrade-install-component-meeting-notes-from-may-18th-2021/)󠁿 On Tuesday May 18, the component held a meeting in the [#core-auto-updates](https://wordpress.slack.com/archives/CULBN711P/p1583863308013300) 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/) channel. You can read the [conversation in Slack](https://wordpress.slack.com/archives/CULBN711P/p1621357243000100). At this time, the component is tackling two main topics * [Updaters](https://make.wordpress.org/core/2021/05/03/feature-project-updates-on-updating-the-updaters/) * Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of the component Yesterday [@afragen](https://profiles.wordpress.org/afragen/), [@poena](https://profiles.wordpress.org/poena/), [@francina](https://profiles.wordpress.org/francina/), and [@pbiron](https://profiles.wordpress.org/pbiron/) worked/discussed the following tickets: * [#14781](https://core.trac.wordpress.org/ticket/14781) – The ticketticket Created for both bug reports and feature development on the bug tracker. was discussed also during the previous chat. It was decided to close it and follow [the best practices laid out in the plugin handbook](https://developer.wordpress.org/plugins/plugin-basics/best-practices/#folder-structure). * [#20944](https://core.trac.wordpress.org/ticket/20944) – The ticket was closed. The maintainers don’t see an elegant way to automate this action at this time. The solution is to re-activate the 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. from the CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. or via FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. [https://codex.wordpress.org/FTP_Clients](https://codex.wordpress.org/FTP_Clients). * [#17301](https://core.trac.wordpress.org/ticket/17301) – A method or instructions on how to test would be good. Added a note asking for testing info in the ticket. * [#51823](https://core.trac.wordpress.org/ticket/51823) and [#51857](https://core.trac.wordpress.org/ticket/51857)– The issue in the first ticket can not be reproduced or addressed without more details. [@francina](https://profiles.wordpress.org/francina/) will investigate with [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) since the ticket mentions the Yoast plugin. As for the second ticket, [@afragen](https://profiles.wordpress.org/afragen/) pointed out that there were issues in the copying of the downloaded plugin or the plugin was incompletely downloaded and it’s hard to determine. The feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/) [Rollback Update Failure](https://wordpress.org/plugins/rollback-update-failure/) is an attempt to restore the previous existing plugin in the event of a failure. He created a Gist to force a failure to see how the feature plugin works. [https://gist.github.com/afragen/80b68a6c8826ab37025b05d4519bb4bf](https://gist.github.com/afragen/80b68a6c8826ab37025b05d4519bb4bf)– If you try it, please add your comments in the tickets. * [#15134](https://core.trac.wordpress.org/ticket/15134), [#29408](https://core.trac.wordpress.org/ticket/29408), and [#36710](https://core.trac.wordpress.org/ticket/36710) are all related to symlinks. [@pbiron](https://profiles.wordpress.org/pbiron/) will evaluate those and see if he can close a couple of them in favor of keeping of single ticket open. See you next week! [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/), [#updater](https://make.wordpress.org/core/tag/updater/), [#upgrade-install](https://make.wordpress.org/core/tag/upgrade-install/) [ ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/) 8:08 pm _on_ May 18, 2021 Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Dev Chat Agenda for May 19, 2021](https://make.wordpress.org/core/2021/05/18/dev-chat-agenda-for-may-19-2021/)󠁿 Here is the agenda for this week’s developer meetings to occur at the following times: [May 19, 2021 at 5:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210519T0500) and [May 19, 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210519T2000). ## Blogblog (versus network, site) Post Highlights * [A Week in Core – May 17, 2021](https://make.wordpress.org/core/2021/05/17/a-week-in-core-may-17-2021/) * [What’s new in Gutenberg 10.6? (12 May)](https://make.wordpress.org/core/2021/05/14/whats-new-in-gutenberg-10-6-12-may/) * [Introducing the WordPress CSS Audit Tool](https://make.wordpress.org/core/2021/05/17/introducing-the-wordpress-css-audit-tool/) * [Core Editor](https://make.wordpress.org/core/2021/05/17/core-editor-meeting-12-may-2021/) meeting summary ## Blog posts that need feedback * [Help Test the Widgets Editor for WordPress 5.8](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/) ## 󠀁[5.8 Schedule Review](https://make.wordpress.org/core/5-8/)󠁿 * **Final Alpha Scrub focused on [features and enhancements](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&type=enhancement&type=feature+request&type=task+(blessed)&milestone=5.8&col=id&col=summary&col=type&col=status&col=owner&col=priority&col=component&col=changetime&col=keywords&order=changetime) before Feature Freeze on [May 24, 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210524T2000)** * **Feature Freeze in 6 days on Tuesday, May 25th** * 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 in 20 days on Tuesday, June 8th * 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/35/?output_format=md#alpha-beta). 1 in 41 days on Tuesday, June 29th * 5.8 release in 62 days on Tuesday, July 20th ## Components check-in and status updates * 5.8 plans and help needed * Check-in with each component for status updates. * Poll for components that need assistance. ## Open Floor Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above? Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly. This meeting happens in the [#core](https://wordpress.slack.com/messages/C02RQBWTW) channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/). _Props [@desrosj](https://profiles.wordpress.org/desrosj/) for peer review._ [#5-8](https://make.wordpress.org/core/tag/5-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/jffng/) [Jeff Ong](https://profiles.wordpress.org/jffng/) 6:48 pm _on_ May 18, 2021 Tags: [make.wordpress.org/themes ( 26 )](https://make.wordpress.org/core/tag/make-wordpress-org-themes/), [p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Block-based Themes Meeting Agenda](https://make.wordpress.org/core/2021/05/18/xpost-block-based-themes-meeting-agenda/)󠁿 X-post from [+make.wordpress.org/themes](https://make.wordpress.org/themes/): [Block-based Themes Meeting Agenda](https://make.wordpress.org/themes/2021/05/18/block-based-themes-meeting-agenda/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/36/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/34/?output_format=md)