I’ve arrived at the difficult decision to cancel the inaugural WordCamp Asia event, which was planned to take place in Bangkok on February 21st. The excitement and anticipation around this event have been huge, but there are too many unknowns around the health issues unfolding right now in the region to explicitly encourage a large public gathering bringing together over 1,300 people from around the world.
We’re going to explore if speakers — including myself — can do our sessions with the same content and at the same time that was originally planned, just online instead of in-person so we can achieve our goal of bringing the pan-Asian community closer together without putting anyone’s health at additional risk.
Regardless, I greatly appreciate the work everyone — from organizers to attendees, speakers to sponsors — put into making this a big success. So many people have come together to create an event to inspire and connect WordPressers, and I am confident that this passion will carry through into the event next year. Our thoughts are with everyone affected by the virus so far, and we sincerely hope that everything is resolved quickly so that this precaution looks unnecessary in hindsight.
WordPress 5.4 Beta 1 is now available for testing!
This software is still in development, so we don’t recommend running it on a production site. Consider setting up a test site to play with the new version.
WordPress 5.4 is slated for release on March 31, 2020, and we need your help to get there!
While the primary goal for 2020 is full-site editing with blocks, contributors to WordPress are working across every area of the project to ensure the software continues moving forward.
Testing for bugs is an important part of polishing the release during the beta stage and a great way to contribute. Here are some of the big changes and features to pay close attention to while testing.
Block Editor: features and improvements
WordPress 5.4 Core will merge ten releases of the Gutenberg plugin. This means there’s a long list of exciting new features. Here are just a few:
Two new blocks: social links and buttons.
More color options for Button, Cover, Group and Column blocks .
Tools for adding featured images in the Latest Posts block.
Easier navigation in the block breadcrumbs.
Some additional changes to make note of:
On mobile, the toolbar stays on top, so you can’t lose it.
Easier image sizing in the Gallery block.
Drag-and-drop images into the featured-image box.
Several new APIs.
Friendlier offline error messages on REST API request failures.
Table block captions.
You can now color just parts of the text in any RichText block.
Accessibility improvements
Easier multi-block selection.
Support for changing an image’s title attribute within the Image block.
Easier tabbing. This had been one of the editor’s biggest accessibility problems, but now tabbing works with the block’s sidebar.
Visual switch between Edit and Navigation modes and enable screen reader announcements.
To see all of the features for each release in detail check out the release posts: 6.6, 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4 and 7.5.
Continuing efforts to improve performance
The block editor team has achieved a 14% loading time reduction and 51% time-to-type reduction, for a particularly sizable post (~ 36,000 words, ~1,000 blocks) since WordPress 5.3.
Wait! There’s more
Site Health
When a project powers 34% of the world’s websites, there must be a focus on security. This is why contributors continue working so hard on the Site Health Project.
WordPress 5.4 adds a widget on the dashboard that warns administrators of potential issues that could affect their site’s performance or security. A call-to-action button directs them to the Site Health screen for details and suggested fixes.
Accessibility improvements
WordPress strives to improve accessibility with every release, and this release is no different. Version 5.4 will contain the following accessibility enhancements:
Better focus management in Menu, Customizer and Site Health screens, to fix some existing keyboard navigation issues.
Easier keyboard navigation for better semantics in the Media modal.
An easier-to-read Privacy Policy Guide.
For Developers
5.4 also contains a bunch of developer focused changes.
Calendar Widget
The HTML 5.1 specification mandates that a <tfoot> tag must follow <tbody> tag (which was not the case in the calendar widget). WordPress 5.4 moves the navigation links to a <nav> HTML element immediately following the <table> element in order to produce valid HTML.
apply_shortcodes() as an alias for do_shortcode()
Instead of using do_shortcode(), apply_shortcodes() should be utilized instead. While do_shortcode() is not being deprecated, the new function delivers better semantics.
Better favicon handling
Now favicon requests can be managed with more flexibility. Administrators can choose a favicon in the Customizer, or upload a /favicon.ico file. The WordPress logo will always load as a fallback.
Other changes for developers
Clearer information about errors in wp_login_failed.
Site ID has been added to the newblog_notify_siteadmin filter for multisite installs.
Support has been added for the required WordPress and PHP version headers in themes.
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac where you can also find a list of known bugs.
Following an action-packed December, 2020 is off to a fine start with some new releases and announcements. Read on to find out what happened in the WordPress project in January.
Release of Gutenberg 7.2 & 7.3
Gutenberg 7.2, the first Gutenberg release of 2020, was deployed on January 8th and included over 180 pull requests from more than 56 contributors. This was followed soon after by Gutenberg 7.3. New features include a new Buttons block, support in adding links to Media & Text block images, improvements to the Navigation and Gallery blocks, performance improvements, and accessibility enhancements. These releases also included many additional enhancements, fixes, new APIs, documentation, and more.
In June last year, a team of contributors proposed a feature plugin that would bring standardized XML sitemaps to WordPress Core. Since then, the team has been working to bring this to reality and have now published a working plugin to demonstrate this new capability.
The plugin is still in development, but the included features already provide much-needed functionality from which all WordPress sites can benefit. You can install the plugin from your WordPress dashboard or download it here.
The Theme Review Team has announced that they will be holding bi-weekly meetings in the #themereview channel focused on discussing block-based themes. If you are interested in discussing themes within the context of Gutenberg’s full-site editing framework, this will be the place to do so! The first meeting will be held on Wednesday, February 5, at 16:00 UTC.
The Core team has started work on WordPress 5.4 and kicked off their planning with a summary post. You can follow all the v5.4 updates by watching the version tag on the Core team blog.
The inaugural WordCamp Asia event is taking place in February. This will be the largest WordPress event in the region, bringing together around 1,500 WordPress enthusiasts from around the world.
A feature plugin has been proposed that introduces lazy-loading images to WordPress Core, which will be a huge step forward in improving performance all across the web.
The Core team has put together an extensive and informative FAQ to help new contributors get involved in contributing to the project.
One key priority for Gutenberg is the ability to control the block editor. There are already a number of APIs that control the experience, but there is a lack of consistency and missing APIs. A method to address this has been proposed.
You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.
Meet Robert Cheleuka
Robert is a self-taught graphic and motion designer turned web designer (and aspiring web developer) from Malawi, Africa. Over the years, he has grown fond of WordPress and has become a loyal user. Still, the journey is rough.
Robert Cheleuka
Malawi
Malawi is one of the poorest countries in the world. A tiny landlocked country with a population of 17 million, it’s largely rural and still considered a developing country. The average entry-level monthly pay for most skilled jobs is about $110. If you’re employed full-time in the creative industry and if you’re very lucky, you might be able to earn more than that. Employees earning more than $300 a month are rare to non-existent.
Robert has been a freelance graphic designer since about 2011. He started by doing gigs from his dorm in college and from home. Earnings from his freelance jobs increased his interest in entrepreneurship and he started to consider starting his own creative agency.
How Robert was introduced to WordPress
Robert first came into contact with WordPress in 2014 when he and a friend started a local tech blog. Before that, all he knew was basic, outdated HTML from high school and some knowledge of Adobe Dreamweaver. They decided to use WordPress, and their new blog looked like it came from the future. They used a theme from the repo and got such positive feedback from the blog they decided to open a content and media publishing agency.
While they got a few web redesign jobs thanks to the exposure the blog brought, they lacked the administrative and business skills needed and ended up going their separate ways. Then in his first real job after college Robert finally took it upon himself to learn the ins and outs of WordPress. He learned how to install WordPress on a server and did some research on customizing themes.
With that knowledge alone he got his first web design clients and started earning nearly as much as he did at his job. Robert soon realized that free WordPress themes would only take him so far, especially with his limited code skills.
Because in Malawi only people who travel abroad have access to credit cards, paying for premium themes was impossible. Like many WordPress designers in developing countries, Robert turned to using pirated themes instead. He knew that was both unsafe and unethical, and decided to learn how to code. Knowing how to build themes from scratch would surely help him rise above the competition.
The WordPress community from Robert’s perspective
Robert doesn’t have a lot of interaction with the WordPress community. Although he would search for solutions from blogs about WordPress he had never actually talked to or asked anyone from the community for a solution.
Robert believes that this isolation is the result of a glass ceiling — the WordPress community is partially online and partially in-person, but there isn’t a local group in Malawi. And because Malawi, like many other developing nations, lacks a way to pay online many can’t access premium support, online learning, or most other types of professional development. No matter how welcoming the people of WordPress might be, it can still feel like it mostly belongs to those with enough privilege to conduct business on the internet.
WordPress & inclusion
As most freelancers know, it’s really hard to learn while you also still need to earn. Add pitching to clients and shipping graphic design projects… there are only so many hours in a day.
Robert didn’t have a programming background and had always been more of a creative person. In order to grow as a web designer/developer, he needed to learn PHP. Again, without access to a credit card, that was complicated. Also, free coding training wasn’t as widely available as it is now.
Robert wishes that more developers would consider alternative ways for users who cannot pay for courses, themes, or plugins (whether that’s because of available infrastructure or otherwise). He wishes that WordPress tutors and developers would open up ways to accommodate aspiring learners in developing countries who cannot access plugins, courses, and themes, to be able to give back and to participate at another level.
WordPress has allowed him to build an income he would have no other way of earning and it makes a huge difference. He believes sharing stories like his will hopefully make WordPress products and services become more universally available. In addition, he hopes that more aspiring, self-taught developers will find courage in reaching out to connect with others out there.
This post is based on an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.
Meet more WordPress community members over at HeroPress.com!
CMX is one of the largest professional organizations dedicated to community builders. The awards were open to public nomination, and finalists were chosen by panels of their peers in the CMX community.
Andrea has been a vital community strategist for the WordPress project since 2011. Her work to build and support a vibrant community has played a part in the success around the popular open source CMS. Her work is sponsored by Automattic, where she leads a team that focuses on educational efforts, funding, and in-person community-driven events that serve a global base.
Josepha has been the Executive Director of the WordPress project since 2019. Her work to coordinate and guide volunteer efforts spans 20 teams and involves thousands of volunteers. Her work is also sponsored by Automattic, where she leads the open source division that focuses on all aspects of open source contribution including design, development, volunteer engagement, and the health of the overall WordPress ecosystem.
Votes are Open
Final recipients are chosen with open voting — if you feel like either Andrea or Josepha have had an impact on your careers, your trajectory in the WordPress project, or the health of WordPress as a whole, there are three ways you can show your support:
Stop by and vote for them (Andrea here, Josepha here)!
Share this post with your own communities!
Tweet some inspirational thoughts about your time/experience/learnings with WordPress (using #WordPress, naturally)!
Thank You Notes
A lot of care and passion goes into making the WordPress Project as fantastic as it is. I think these awards are a reflection of how wonderful the community and ecosystem are, and I appreciate everyone’s continued trust in my stewardship!
Josepha Haden Chomphosy
WordPress community organizers are some of the most generous and creative people in the world — working with them is exciting and interesting every day. I’m humbled by this nomination; thank you!
As 2019 draws to a close and we look ahead to another exciting year let’s take a moment to review what the WordPress community achieved in December.
WordPress 5.3.1 and 5.3.2 Releases
The WordPress 5.3.1 security and maintenance release was announced on December 13. It features 46 fixes and enhancements. This version corrects four security issues in WordPress versions 5.3 and earlier. Shortly afterwards, WordPress 5.3.2 was released, addressing a couple high severity Trac tickets, and includes 5 fixes and enhancements, so you’ll want to upgrade. You can read more about these releases in the announcements for 5.3.1 and 5.3.2.
Update on the Nine Core Projects for 2019
At the end of 2018, @mattannounced the nine projects that would be the main focus areas for Core development in the next year. Have we made progress? Yes! @chanthabouneposted a full update on the team’s work. In brief, two of the projects have been completed and shipped in major releases, four are targeted for release in versions 5.4 and 5.5 of WordPress, and the remaining three have seen significant progress but are not yet slated for completion. These will continue to see progress throughout 2020.
The Core team has published a tentative release calendar for 2020 and 2021. This is intended to provide the community with more information about what lies ahead.
The schedule is considered tentative because there are always variables that could affect these plans — not least that the Core team may need more time to finish the work planned for a release.
Initial Documentation for Block-Based WordPress Themes
The Gutenberg team has started working on the initial documentation for what block-based themes might look like, marking a significant change in the way themes are conceptualized. With full-site editing now a realistic goal for WordPress, themes will certainly look different in the future.
It’s been a busy month for Gutenberg! Version 7.0, including a new navigation block, was announced on November 27. This was followed by version 7.1, announced on December 11; it includes 161 merged pull requests that offer a fresh UI to new users, an option to switch between edit and navigation modes, captions for the table block, and many other enhancements.
On December 2, the BuddyPress Beta Tester plugin was added to the WordPress.org plugins directory. This feature is a great way for the WordPress community to provide early feedback on releases.
You can download the plugin now. If you find that something is not working as expected during your beta tests, let the BuddyPress team know by submitting a ticket on the Development Tracker or posting a new topic in the BuddyPress support forums.
An Update on the Block Directory in the WordPress Editor
The Design team received lots of excellent feedback on the early concepts for the Block Directory. This feedback was incorporated into a Version 1 update to the #block-directory project. The Block Directory is to be included in WordPress 5.5, which is slated for August 2020. To learn more about the Block Directory, check out this announcement post and help out by sharing your feedback.
This maintenance release features 5 fixes and enhancements.
WordPress 5.3.2 is a short-cycle maintenance release. The next major release will be version 5.4.
You can download WordPress 5.3.2 by clicking the button at the top of this page, or visit your Dashboard → Updates and click Update Now.
If you have sites that support automatic background updates, they’ve already started the update process.
Maintenance updates
Shortly after WordPress 5.3.1 was released, a couple of high severity Trac tickets were opened. The Core team scheduled this quick maintenance release to resolve these issues.
Main issues addressed in 5.3.2:
Date/Time: Ensure that get_feed_build_date() correctly handles a modified post object with invalid date.
Uploads: Fix file name collision in wp_unique_filename() when uploading a file with upper case extension on non case-sensitive file systems.
Media: Fix PHP warnings in wp_unique_filename() when the destination directory is unreadable.
Administration: Fix the colors in all color schemes for buttons with the .active class.
Posts, Post Types: In wp_insert_post(), when checking the post date to set future or publish status, use a proper delta comparison.
During the State of the Word at WordCamp US 2019, Matt Mullenweg shared that Gutenberg was used to create his slides and the presentation was powered by the Slides plugin. Using WordPress to power a slide deck isn’t an obvious choice, so we wanted to showcase the process and give some tips for making slide layouts using Gutenberg.
This post is co-written by Ella and Tammie, who (along with Mel, Mark, Enrique, Qand a cast of supporters) helped create this year’s State of the Word slide deck.
How it Started
Ella Van Durpe was selected to speak at JSConf and ReactEurope and wanted slides for her presentation.
In the past, she’d used Reveal.js to create slides and enjoyed the freedom to create anything using HTML, CSS and JavaScript. These languages were comfortable, familiar, and also can be published on the web in their native format.
For these new presentations, she wanted to use Reveal.js again but didn’t feel like writing all the HTML by hand. Creating blocks of content visually, without having to actually write any code, which can be published natively to the web, is exactly what Gutenberg was built for.
The plugin was prototyped quickly, with hardcoded styles on the slides and zero options. At the end of each presentation, Ella shared a brief demo of the Gutenberg-based slides and the audience was amazed.
As WordCamp US approached, Ella suggested that her plugin be used for State of the Word. Since it was such a hit with her audience members, it seemed like this would be a great chance to share it with the WordPress community as a whole.
This security and maintenance release features 46 fixes and enhancements. Plus, it adds a number of security fixes—see the list below.
WordPress 5.3.1 is a short-cycle maintenance release. The next major release will be version 5.4.
You can download WordPress 5.3.1 by clicking the button at the top of this page, or visit your Dashboard → Updates and click Update Now.
If you have sites that support automatic background updates, they’ve already started the update process.
Security updates
Four security issues affect WordPress versions 5.3 and earlier; version 5.3.1 fixes them, so you’ll want to upgrade. If you haven’t yet updated to 5.3, there are also updated versions of 5.2 and earlier that fix the security issues.
Props to Daniel Bachhuber for finding an issue where an unprivileged user could make a post sticky via the REST API.
Props to Simon Scannell of RIPS Technologies for finding and disclosing an issue where cross-site scripting (XSS) could be stored in well-crafted links.
Props to the WordPress.org Security Team for hardening wp_kses_bad_protocol() to ensure that it is aware of the named colon attribute.
Props to Nguyen The Duc for discovering a stored XSS vulnerability using block editor content.
Maintenance updates
Here are a few of the highlights:
Administration: improvements to admin form controls height and alignment standardization (see related dev note), dashboard widget links accessibility and alternate color scheme readability issues (see related dev note).
Block editor: fix Edge scrolling issues and intermittent JavaScript issues.
Bundled themes: add customizer option to show/hide author bio, replace JS based smooth scroll with CSS (see related dev note) and fix Instagram embed CSS.
Date/time: improve non-GMT dates calculation, fix date format output in specific languages and make get_permalink() more resilient against PHP timezone changes.
Embeds: remove CollegeHumor oEmbed provider as the service doesn’t exist anymore.
External libraries: update sodium_compat.
Site health: allow the remind interval for the admin email verification to be filtered.
Uploads: avoid thumbnails overwriting other uploads when filename matches, and exclude PNG images from scaling after upload.
Users: ensure administration email verification uses the user’s locale instead of the site locale.
You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.
Meet Jill Binder
Jill Binder never meant to become an activist. She insists it was an accident.
Despite that, Jill has led the Diversity Outreach Speaker Training working group in the WordPress Community team since 2017. This group is dedicated to increasing the number of women and other underrepresented groups who are stepping up to become speakers at WordPress Meetups, WordCamps, and events.
Jill’s back story
Internship
Jill’s WordPress story begins in 2011, in Vancouver, Canada. Jill secured an internship for her college program, working on a higher education website that was built in WordPress. As a thank you, her practicum advisor bought Jill a ticket to WordCamp Vancouver 2011: Developer’s Edition. After that Jill began freelancing with WordPress as a Solopreneur.
First steps in the WordPress community
The following year her internship advisor, who had become a client, was creating the first ever BuddyCamp for BuddyPress. He asked Jill to be on his organizing team. At that event she also moderated a panel that had Matt Mullenweg on it. Then, Jill was invited to be on the core organizing team for WordCamp Vancouver.
Part of this role meant reviewing and selecting speakers. From 40 speaker applications that could be a fit the team had to pick only 14 to speak.
The diversity challenge when selecting speakers
For anyone who has organized a conference, you know that speaker selection is hard. Of the 40 applications, 7 were from women, and the lead organizer selected 6 of those to be included in the speaker line up.
At this point Jill wasn’t aware that very few women apply to speak at tech conferences and suggested selection should be made on the best fit for the conference. The team shared that not only did they feel the pitches were good and fit the conference, but they also needed to be accepted or the Organizers would be criticized for a lack of diversity.
Selecting women for fear of criticism is embarrassing to admit, but that’s how people felt in 2013.
By the time the event happened, though, the number of women speakers dropped to 4. And with an additional track being added, the number of speakers overall was up to 28. Only 1 speaker in 7 was a woman (or 14%) and attendees did ask questions and even blogged about the lack of representation.
What keeps women from applying?
Later that year at WordCamp San Francisco—the biggest WordCamp at the time (before there was a WordCamp US)—Jill took the opportunity to chat with other organizers about her experience. She found out that many organizers had trouble getting enough women to present.
Surprisingly Vancouver had a high number of women applicants in comparison to others, and the consensus was more would be accepted if only more would apply.
Jill decided that she needed to know why this was happening? Why weren’t there more women applying? She started researching, reading, and talking to people.
Though this issue is complex, two things came up over and over:
“What would I talk about?”
“I’m not an expert on anything. I don’t know enough about anything to give a talk on it.”
A first workshop with encouraging results
Then Jill had an idea. She brought up the issue at an event and someone suggested that they should get women together in a room and brainstorm speaker topics.
So Jill became the lead of a small group creating a workshop in Vancouver: the talented Vanessa Chu, Kate Moore Hermes, and Mandi Wise. In one of the exercises that they created, participants were invited to brainstorm ideas—this proved that they had literally a hundred topic ideas and the biggest problem then became picking just one!
In the first workshop, they focussed on:
Why it matters that women (added later: diverse groups) are in the front of the room
The myths of what it takes to be the speaker at the front of the room (aka beating impostor syndrome)
Different presentation formats, especially story-telling
Finding and refining a topic
Tips to become a better speaker
Leveling up by speaking in front of the group throughout the afternoon
Vancouver Workshop 2014
Leading to workshops across North America and then the world
Other cities across North America heard about the workshop and started hosting them, adding their own material.
Many women who initially joined her workshop wanted help getting even better at public speaking. So Jill’s Vancouver team added in some material created from the other cities and a bit more of their own. Such as:
Coming up with a great title
Writing a pitch that is more likely to get accepted
Writing a bio
Creating an outline
At WordCamp Vancouver 2014—only one year since Jill started—there were 50% women speakers and 3 times the number of women applicants! Not only that, but this WordCamp was a Developer’s Edition, where it’s more challenging to find women developers in general, let alone those who will step up to speak.
More work is needed!
Impressive as those results were, the reason Jill is so passionate about this work is because of what happened next:
Some of the women who attended the workshop stepped up to be leaders in the community and created new content for other women.
A handful of others became WordCamp organizers. One year Vancouver had an almost all-female organizing team – 5 out of 6!
It also influenced local businesses. One local business owner loved what one of the women speakers said so much that he hired her immediately. She was the first woman developer on the team, and soon after she became the Senior Developer.
Diversity touches on many levels
Jill has seen time and again what happens when different people speak at the front of the room. More people feel welcome in the community. The speakers and the new community members bring new ideas and new passions that help to make the technology we are creating more inclusive. And together we generate new ideas that benefit everyone.
This workshop was so successful, with typical results of going from 10% to 40-60% women speakers at WordCamps, that the WordPress Global Community Team asked Jill to promote it and train it for women and all diverse groups around the world. In late 2017, Jill started leading the Diverse Speaker Training group (#wpdiversity).
Dozens of community members across the world have now been trained to lead the workshop. With now dozens of workshops worldwide, for WordPress and other open source software projects as well, there is an increase in speaker diversity.
WordCamp US 2019
As a result of the success, Jill is now sponsored to continue the program. The first sponsor is Automattic. She’s proud of how the diversity represented on the stage adds value not only to the brand but also in the long-term will lead to the creation of a better product. She’s inspired by seeing the communities change as a result of the new voices and new ideas at the WordPress events.
Jill’s leadership in the development and growth of the Diversity Outreach Speaker Training initiative has had a positive, measurable impact on WordPress community events worldwide. When WordPress events are more diverse, the WordPress project gets more diverse — which makes WordPress better for more people.”
Andrea Middleton, Community organizer on the WordPress open source project
This post is based on an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.
Meet more WordPress community members over at HeroPress.com!
Correction: December 7, 2019 The original article mentioned the team Jill lead, but did not mention the team members who joined her. Those have been added. Apologies to Vanessa, Kate, and Mandi. 🙂
