The month of March was both a tough and exciting time for the WordPress open-source project. With COVID-19 declared a pandemic, in-person events have had to adapt quickly – a challenge for any community. March culminated with the release of WordPress 5.4, an exhilarating milestone only made possible by dedicated contributors. For all the latest, read on. <\/p>\n\n\n\n
WordPress 5.4 \u201cAdderley\u201d was released on March 31<\/a> and includes a robust list of new blocks, enhancements, and new features for both users and developers. The primary focus areas of this release included the block editor, privacy, accessibility, and developer improvements, with the full list of enhancements covered in the 5.4 field guide<\/a>.<\/p>\n\n\n\n Want to get involved in building WordPress Core? Follow the Core team blog<\/a>, and join the #core channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n It\u2019s been another busy month for Gutenberg, this time with the release of Gutenberg 7.7<\/a> and 7.8<\/a>. Gutenberg 7.7 introduced block patterns – predefined block layouts that are ready to use and tweak. This is an important step towards Full Site Editing, which is currently targeted for inclusion in WordPress 5.6. As a first iteration, you can pick and insert patterns from the Block Patterns UI, which has been added as a sidebar plugin.<\/p>\n\n\n\n Gutenberg 7.7 also includes a refresh of the Block UI, which better responds to the ways users interact with the editor. For more information on the User UI and Block Patterns, read this summary of the most recent Block-Based Themes meeting<\/a>. Gutenberg 7.8, introduced on March 25, further enhanced this Block UI redesign. Both releases also included a suite of improvements, bug fixes, new APIs, documentation, and more!<\/p>\n\n\n\n Want to get involved in building Gutenberg? Follow the Core team blog<\/a>, contribute to Gutenberg on GitHub<\/a>, and join the #core-editor channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n In early March, the Community team issued new recommendations for event organizers<\/a> in light of growing concerns around COVID-19. Following this guidance, and with COVID-19 declared a pandemic, WordPress community organizers reluctantly but responsibly postponed or canceled their upcoming WordCamps<\/a> and meetups.<\/p>\n\n\n\n As community events are an important part of the WordPress open-source project, the Community team made suggestions for taking charity hackathons online<\/a>, proposed interim adjustments<\/a> to existing community event guidelines, and provided training for online conference organizing<\/a> with Crowdcast. The team is currently working on building a Virtual Events Handbook<\/a> that will continue to support WordPress community organizers at this time. <\/p>\n\n\n\n Want to get involved with the WordPress Community team, host your own virtual WordPress event, or help improve the documentation for all of this? Follow the Community team blog<\/a>, learn more about virtual events<\/a>, and join the #community-events channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n Last month, an experimental feature<\/a> was added to Trac, WordPress Core\u2019s bug-tracking system, to improve collaboration between Trac and GitHub. This month, to help make tracking contributions to the WordPress project across multiple locations easier, there is a new option<\/a> to connect your GitHub account to your WordPress.org profile. This connection allows for more accurate acknowledgement and recognition of contributors. You can connect your GitHub account to your WordPress.org account by editing your WordPress.org profile.<\/p>\n\n\n\n For more information and instructions on how to connect your accounts, read the announcement post<\/a>.<\/p>\n\n\n\n Defined coding standards is an important step in creating the consistent codebase needed to prepare for requiring PHP 7.x for WordPress Core. As such, coding standards have been proposed<\/a> for implementation in WordPress Coding Standards 3.0.0. This includes new proposed standards for namespace declarations, import use statements, fully qualified names in inline code, traits and interfaces, type declarations, declare statements\/strict typing, the ::class constant, operators, and more. <\/p>\n\n\n\n Want to get involved or view the full list of currently proposed new coding standards? Visit and add your feedback to the post on updating the Coding standards for modern PHP<\/a> and follow the Core team blog<\/a>.<\/p>\n\n\n\nReleases of Gutenberg 7.7 and 7.8<\/h2>\n\n\n\n
WordCamp cancellations and shift to online events<\/h2>\n\n\n\n
Link your GitHub profile to WordPress.org<\/h2>\n\n\n\n
Modernizing WordPress coding standards<\/h2>\n\n\n\n
\n\n\n\nFurther Reading:<\/h2>\n\n\n\n