June has certainly been a busy month in the WordPress community \u2014 aside from holding the largest WordPress event ever, the project has hit a number of significant milestones and published some big announcements this past month.<\/p>\n\n\n\n
WordCamp Europe 2019 took place on June 20-22. It was the largest WordPress event ever, with 3,260 tickets sold and 2,734 attendees. The attendees came from 97 different countries and 1,722 of them had never attended WordCamp Europe before.<\/p>\n\n\n\n
The event featured 60 speakers who delivered talks and workshops on a variety of topics over two conference days, most notably Matt Mullenweg<\/a>\u2019s keynote that included an update on the current status of WordPress Core development, along with a lively Q&A session. The full session from the live stream is available to watch online<\/a>.<\/p>\n\n\n\n For its eighth year, WordCamp Europe will take place in Porto, Portugal<\/a>. The 2020 edition of the event will be held on June 4-6. If you would like to get involved with WordCamp Europe next year, fill out the organizer application form<\/a>. <\/p>\n\n\n\n A proposal this month<\/a> suggested bringing XML sitemap generation into WordPress Core. This is a feature that has traditionally been handled by plugins, which has resulted in many different implementations across different sites. It also means that many sites do not have XML sitemaps, which can be a problem because they are hugely important to having your site correctly indexed by search engines.<\/p>\n\n\n\n The proposal details how core sitemaps would be structured and how the team would build them, as well as what aspects of WordPress would not be considered appropriate information to be included.<\/p>\n\n\n\n Want to get involved in building this feature? Comment on the proposal<\/a>, follow the Core team blog<\/a>, and join the #core channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n The WordPress community of Spain has worked hard<\/a> to make the es_ES locale<\/a> the first in the world to fully localize all of WordPress Core along with all Meta projects, apps, and the top 200 plugins. This is made possible by having the largest translation team out of any locale, consisting of 2,951 individual contributors.<\/p>\n\n\n\n Want to get involved in translating WordPress into our locale? Find your locale on the translation platform<\/a>, follow the Polyglots team blog<\/a>, and join the #polyglots channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n On June 18, v5.2.2 of WordPress was released<\/a> as a maintenance release, fixing 13 bugs and improving the Site Health feature that was first published in v5.2. If your site has not already been automatically updated to this version, you can download the update<\/a> or manually check for updates in your WordPress dashboard. Thanks to JB Audras<\/a>, Justin Ahinon<\/a>, and Mary Baum<\/a> for co-leading this release, as well as the 30 other individuals who contributed to it.<\/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 On June 27, e2e (end to end) testing was introduced<\/a> to WordPress and included in the continuous integration pipeline. E2e testing, which has been successfully used by Gutenberg, is used to simulate real user scenarios and validate process flows. Currently, the setup requires Docker<\/a> to run, and a number of e2e test utilities are already available in the @wordpress\/e2e-test-utils<\/a> package, in the Gutenberg repository. <\/p>\n\n\n\n Want to use this feature? The more tests that are added, the more stable future releases will be! Follow the the Core team blog<\/a>, and join the #core-js channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n Following a proposal for theme feature repositories<\/a>, an update to the features package was announced<\/a>. Two new packages have been created that require code review and testing. The first is an Autoload Package, a foundational package for theme developers who are not currently using Composer (although Composer<\/a> is recommended instead of this package). The second is a Customizer Section Button Package that allows theme authors to create a link\/button to any URL.<\/p>\n\n\n\n There are other proposed ideas for packages that require feedback and additional discussion. Want to add your suggestions and thoughts? Join the conversation on the Theme Review team blog<\/a> and join the #themereview channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\nProposal for XML Sitemaps in WordPress Core<\/h2>\n\n\n\n
Translation Milestone for the Spanish Community<\/h2>\n\n\n\n
WordPress 5.2.2 Maintenance Release<\/h2>\n\n\n\n
Full End to End Tests for WordPress Core<\/h2>\n\n\n\n
Feature Packages from the Theme Review Team<\/h2>\n\n\n\n
\n\n\n\nFurther Reading:<\/h2>\n\n\n\n