{"id":6987,"date":"2019-06-04T10:21:27","date_gmt":"2019-06-04T10:21:27","guid":{"rendered":"https:\/\/wordpress.org\/news\/?p=6987"},"modified":"2021-06-04T12:01:30","modified_gmt":"2021-06-04T12:01:30","slug":"the-month-in-wordpress-may-2019","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2019\/06\/the-month-in-wordpress-may-2019\/","title":{"rendered":"The Month in WordPress: May 2019"},"content":{"rendered":"\n
This month saw the 16th anniversary since the launch of the first release of WordPress<\/a>. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a significant global event.<\/p>\n\n\n\n WordPress 5.2 \u201cJaco\u201d was released on May 7<\/a> shipping some useful site management tools, such as the Site Health Check and PHP Error Protection, as well as a number of accessibility, privacy, and developer updates. You can read the field guide for this release<\/a> for more detailed information about what was included and how it all works. 327 individual volunteers contributed to the release. If you would like to be a part of that number for future releases, follow the Core team blog<\/a> and join the #core channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n WordPress Translation Day is a 24-hour event organised by the Polyglots team<\/a> where community members from all over the world come together to translate WordPress into their local languages. For the fourth edition held on 11 May, 183 brand new contributors joined the Polyglots team from 77 communities across 35 countries in Africa, Asia, Europe, North America, South America, and Oceania. While the WP Translation Day is a great time for focussed contributions to localizing WordPress, but these contributions can happen at any time of the year, so if you would like to help make WordPress available in your local language, follow the Polyglots team blog<\/a> and join the #polyglots channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n The Plugins team has proposed some updates<\/a> to the guidelines for developers on the Plugin Directory. The majority of the proposed changes are intended to address significant issues faced by developers who do not speak English as a first language, making the Plugin DIrectory a more accessible and beneficial place for everyone. The proposal will be open for comments until late June, so the community is encouraged to get involved with commenting on them and the direction they will take the Plugin Directory. If you would like to be involved in this discussion, comment on the proposal<\/a> and join the #plugin review team in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n Since the block editor was first released as part of WordPress Core in v5.0, development has continued in leaps and bounds with a new release every two weeks. The latest update<\/a> includes some great incremental improvements that will be merged into the 5.2.2 release of WordPress along with the other recent enhancements. In addition to the editor enhancements, work has been ongoing in the Gutenberg project to bring the block editing experience to the rest of the WordPress dashboard. This second phase of the project has been going well and the latest update<\/a> shows how much work has been done so far. In addition to that, the Block Library project that aims to bring a searchable library of available blocks right into the editor is deep in the planning phase with a recent update<\/a> showing what direction the team is taking things. If you would like to get involved in planning and development of Gutenberg and the block editor, follow the Core<\/a> and Design<\/a> team blogs and join the #core, #design, and #core-editor channels in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n
\n\n\n\nRelease of WordPress 5.2<\/h2>\n\n\n\n
<\/p>\n\n\n\nA Successful WordPress Translation Day 4<\/h2>\n\n\n\n
<\/p>\n\n\n\nUpdated Plugin Guidelines Proposal<\/h2>\n\n\n\n
<\/p>\n\n\n\nContinued Gutenberg Development<\/h2>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nFurther Reading:<\/h2>\n\n\n\n