{"id":4865,"date":"2017-07-03T11:42:11","date_gmt":"2017-07-03T11:42:11","guid":{"rendered":"https:\/\/wordpress.org\/news\/?p=4865"},"modified":"2021-06-04T12:00:53","modified_gmt":"2021-06-04T12:00:53","slug":"the-month-in-wordpress-june-2017","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2017\/07\/the-month-in-wordpress-june-2017\/","title":{"rendered":"The Month in WordPress: June 2017"},"content":{"rendered":"

We’re starting a new regular feature on this blog today. We’d like to keep everyone up-to-date about the happenings all across the WordPress open source project and highlight how you can get involved, so we’ll be posting a roundup of all the major WordPress news at the end of every month.<\/i><\/p>\n

Aside from other general news, the three big events in June were the release of WordPress 4.8, WordCamp Europe 2017, and the WordPress Community Summit. Read on to hear more about these as well as other interesting stories from around the WordPress world.<\/p>\n


\n

WordPress 4.8<\/h2>\n

On June 8, a week before the Community Summit and WordCamp Europe, WordPress 4.8 was released<\/a>.You can read the Field Guide<\/a> for a comprehensive overview of all the features of this release (the News and Events widget in the dashboard is one of the major highlights).<\/p>\n

Most people would either have their version auto-updated, or their hosts would have updated it for them. For the rest, the updates have gone smoothly with no major issues reported so far.<\/p>\n

This WordPress release saw contributions from 346 individuals; you can find their names in the announcement post<\/a>. To get involved in building WordPress core, jump into the #core channel in the Making WordPress Slack group<\/a>, and follow the Core team blog<\/a>.<\/p>\n

WordCamp Europe 2017<\/h2>\n

WordCamp Europe 2017<\/a> was held in Paris between June 15-17. The event began with a Contributor Day, followed by two days of talks and community goodness. The talks were live-streamed, but you can still catch all the recordings on WordPress.tv<\/a>. The organisers also published a handy wrap-up of the event<\/a>.<\/p>\n

WordCamp Europe exists to bring together the WordPress community from all over the continent, as well as to inspire local communities everywhere to get their own events going \u2014 to that end, the event was a great success, as a host of new meetup groups have popped up in the weeks following WordCamp Europe.<\/p>\n

The work that Contributor Day participants accomplished was both varied and valuable, covering all aspects of the WordPress project \u2014 have a look through the Make blogs<\/a> for updates from each team.<\/p>\n

Finally, we also learned during the event that WordCamp Europe 2018 will be held in Belgrade, Serbia<\/a>, continuing the tradition of exploring locations and communities across the continent.<\/p>\n

WordPress Community Summit<\/h2>\n

The fourth WordPress Community Summit took place during the two days leading up to WordCamp Europe 2017. This event is an invite-only unconference where people from all over the WordPress community come together to discuss some of the more difficult issues in the community, as well as to make plans for the year ahead in each of the contribution teams.<\/p>\n

As the Summit is designed to be a safe space for all attendees, the notes from each discussion are in the process of being anonymized before we publish them on the Summit blog<\/a> (so stay tuned – they\u2019ll show up there over the next few weeks).<\/p>\n

You can already see the final list of topics that were proposed for the event here<\/a> (although a few more were added during the course of the two day Summit).<\/p>\n

WordPress marketing push continues apace<\/h2>\n

As part of the push to be more intentional in marketing WordPress (as per Matt Mullenweg’s 2016 State of the Word<\/a>), the Marketing team has launched two significant drives to obtain more information about who uses WordPress and how that information can shape their outreach and messaging efforts.<\/p>\n

The team is looking for WordPress case studies<\/a> and is asking users, agencies, and freelancers to take a WordPress usage survey. This will go a long way towards establishing a marketing base for WordPress as a platform and as a community \u2014 and many people in the community are looking forward to seeing this area develop further.<\/p>\n

To get involved in the WordPress Marketing team, you can visit their team blog<\/a>.<\/p>\n

New Gutenberg editor available for testing<\/h2>\n

For some time now, the Core team has been hard at work on a brand-new text editor for WordPress \u2014 this project has been dubbed \u201cGutenberg.\u201d The project\u2019s ultimate goal is to replace the existing TinyMCE editor, but for now it is in beta and available for public testing \u2014 you can download it here as a plugin<\/a> and install it on any WordPress site.<\/p>\n

This feature is still in beta, so we don\u2019t recommend using it on a production site. If you test it out, though, you\u2019ll find that it is a wholly different experience to what you are used to in WordPress. It\u2019s a more streamlined, altogether cleaner approach to the text-editing experience than we\u2019ve had before, and something that many people are understandably excited about. Matt Mullenweg discussed the purpose of Gutenberg in more detail during his Q&A at WordCamp Europe<\/a>.<\/p>\n

There are already a few reviews out from Brian Jackson at Kinsta<\/a>, Aaron Jorbin<\/a>, and Matt Cromwell<\/a> (among many others). Keep in mind that the project is in constant evolution at this stage; when it eventually lands in WordPress core (probably in v5.0), it could look very different from its current iteration \u2014 that\u2019s what makes this beta stage and user testing so important.<\/p>\n

To get involved with shaping the future of Gutenberg, please test it out<\/a>, and join the #core-editor channel in the Making WordPress Slack group<\/a>. You can also visit the project\u2019s GitHub repository<\/a> to report issues and contribute to the codebase.<\/p>\n


\n

Further reading:<\/h2>\n