Copy
It's your fave WordPress weekly email, now at issue 87!

<<Name>>, hello!

Welcome back to MasterWP Weekly, your weekly newsletter for WordPress professionals 👋

Alex profile picAlex is enjoying setting up his new office – a beautiful new desk is on its way! Any home office tips are welcome; reply to this email!

Ben profile picBen is still improving his old themes, and almost finished with his new theme. He’s also thinking about his next project. Will it be a WordPress thing, or a React app, or something totally different? He’s not sure yet.

What’s coming up: after 18 months of Gutenberg news, this feels like a week where things are coming to a head. This week's issue is an important one.

- Alex and Ben

SPONSOR

Kinsta is a premium managed WordPress host powered exclusively by Google Cloud Platform. They offer 15+ data center locations, free migrations, 24x7 support, free SSL and CDN, dev-friendly staging environments and SSH, automatic backups, along with unique performance features such as complete resource isolation and automatic scalability.

Get started today with their all-in-one hosting solution at kinsta.com.

WordPress 5.0 Slated for November 19, 2018

5.0 and Gutenberg are getting very close, but the WordPress Accessibility Team Lead has resigned over accessibility concerns

Last week Core Team member Gary Pendergast published a proposed WordPress 5.0 scope and schedule, which included a proposed release date of 19th November 2018, with a “backup date” of 22nd January 2019.

There are two strands to why this is a big deal:

  1. When 5.0 releases, there will be a ton of extra interest in WordPress, many users will use Gutenberg for the first time, and inevitably they’ll be a jump in maintenance and support requests.
  2. Rian Rietveld, the WordPress Accessibility Team Lead, has resigned, citing frustration at, amongst other things "the overall Gutenberg design, where accessibility hasn’t been incorporated in the design process".

These are both huge issues, so let's look at each in turn.

First, the date. The new editor will result in a rise in maintenance and support requests, and the proposed release date is three days before Thanksgiving (a major US holiday). This also coincides with Black Friday/Cyber Monday, two major eCommerce sales days. Thus, many in the US will have scheduled this as family time off, but might find themselves needing to work on Gutenberg issues instead.

Here’s a selection of comments from the release post:

“We are the WordPress 1%. The people we build WordPress for are not in these conversations, nor are they aware of what is happening. They trust WordPress to “do the right thing”. In this case, from my perspective, that is to at least avoid a major release a few days before a major holiday.” - Morten Rand-Hendriksen

“There won’t be a perfect time to release, but there certainly are times we can look at and go “This is probably bad…” I think this is a case of the latter.” - Mika Epstein

“Some of us would like to spend Thanksgiving week with our family and friends and not handling support requests for the users who unwittingly upgrade to 5.0 without knowing how big of a change it is.” - Justin Tadlock

This release date would conveniently get Gutenberg out in time for WordCamp US. Here's Carl Hancock:

“Just going to call… [out] anyone claiming “every date is bad for someone” or “every month has holidays somewhere” when defending possible Nov-Dec WordPress 5.0 release. It is trying to be rammed in for WordCamp U.S. where those November and December holidays are major ones… WordPress isn’t Apple.”

The Tavern also covers some of this reaction in a separate post (to its credit, as it’s indirectly owned by Matt Mullenweg).

This is a tricky one. As we know from WCEU, the release date for Gutenberg has always been as soon as possible, and that probably meant “already happened”. Thus, it is only being released “when ready”, but right before a major holiday and conveniently before WCUS does seem unnecessary. There’s still a lot of work to do, as Gary’s original post covers; but there's also still a lot of accessibility work to do, which brings us to the second strand of this discussion.

As mentioned, yesterday Rian Rietveld resigned as WordPress Accessibility Team Lead over frustration with accessiblity in Gutenberg. This is a really big deal, and hopefully a "wake-up call".

Rian's post covers the issues: the Accessiblity Team has been engaged in Gutenberg from the start, but have been fighting an uphill battle to get accessibility taken seriously or addressed. In some instances where functionality was tested, and then made accessible, it was later changed and made inacessible. This is obviously extremely frustrating.

The Accessiblity Team lacked REACT expertise so focused on training and raising GitHub issues; this positioned accessiblity as a bug which needed fixing rather than something which should be at the core of the design from the start.

A full-time developer focused on accessibility at Automattic is now working full-time on Gutenberg, but arguably retrofitting accessibility at this stage is too late.

At the heart of this issue is not the individual contributors to Gutenberg, but a repeat of the issue we picked up on after "cookiegate" at WordCamp Europe: a growing disconnect between some contributors and the WordPress leadership. Rian addresses this with a section "To Matt Mullenweg":

To Matt Mullenweg I want to say: please take better care of your community, because WordPress is nothing without it. Cherish the people who dedicate their (own) time and who work very hard to make WordPress the best it can be. Don’t ignore or make fun of them, but talk to them, guide them, inform them. Don’t be disconnected from the community, be part of it.

There's rightly been an outpouring of support from the community for Rian and her Team's work. This now needs to turn into action.

I've been writing about Gutenberg "drama" in this newsletter more or less every week for the last 18 months. I don't especially enjoy it and would really like, as John Blackbourn said this week, if the WordPress community – and especially leadership – can learn the lessons from the last two ears, where "the first phase of Gutenberg development has been disastrous from a project management point of view."

I'll leave you with this, from Carole Olinger: "If this attitude [of a lack of respect] towards the people who keep the project alive will not change, #WordPress will loose its most precious and valuable trump: a strong and passionate community!" Nobody wants that. It's time to do something. - Alex.

WordPress 5.0 for Contributors and Committers

The human cost?

As Alex mentioned, the WordPress & Gutenberg merge is underway. It’s going to be a lot of work. Not only does the plugin need to be merged in, but the build processes and other technical issues need to be resolved.

On top of this, there are a bunch of tickets that could not be addressed in the plugin since they rely on changes in core. So they need to be made as well.

But there’s only so many people to work on these things, and the regular core team are less familiar with the Gutenberg code than the people who have been developing it. Plus most of them have jobs and families and lives outside of WordPress.

So working to a short deadline that core developers had no say in is not likely to encourage participation. Only yesterday Rian Rietveld stepped down as Accessibility Lead for the WordPress project - largely due to lack of support from the core team for accessibility.

I’ve made no secret of the fact that I like Gutenberg and think it’s a worthwhile change. In the current state it's not perfect but with improvement and iteration it will become something very special.

Gutenberg requires a change in mindset and development processes, but in the long run I think it’s going to benefit people greatly.

However I am not convinced by deadlines and constant push to release it as soon as possible. There has to be a reason besides wanting it published in time for WordCamp US, but I don’t know what that is.

And if WCUS is the only reason, then perhaps it would be worth slowing down a bit and considering the human cost of getting it done so quickly. - Ben.

WordPress Theme and Plugin Shops are Pioneering the First Layout Blocks for Gutenberg

Great reporting and case studies from the Tavern

This is a great good-news Gutenberg piece, and some great reporting from Sarah at WP Tavern: Sarah looks at some of the newest Gutenberg innovations, and how they’re coming from theme shops who, having typically diversified into plugins in recent years, are perfectly placed to mix design and functionality with new Gutenberg blocks.

We will see a really dominant go-to “extra Gutenberg block plugin” in the near future, and it’s exciting to see all the various offerings come about as various groups try various things. Watch this space! - Alex.

End-to-End Testing with Cypress

Automated Interface Testing

Automated testing is awesome, but it only tells you if discrete functions work. It doesn’t tell you if the interface has been broken or a colour has changed or something that the user actually sees has been altered. This is where software like Selenium come in. But that’s not much fun to use or setup.

I’ve not used it yet but I absolutely plan to. Cypress looks easy to setup, and fun to use, and like it would actually be helpful.

When I do a major app release for Brush Ninja I run through a complex list of manual tests. It takes time, and it’s boring. If I can script it all with Cypress (and I see no reason I can’t) then I can save time, and make it easy to repeat in the future. In fact I can add even more complex tests and still save time.

I’m not sure it would be that useful for WordPress theme testing. Most of the testing there is visual and not functional. Do things look as they should rather than work as they should, however I can see Cypress being ideal for plugins. Definitely one to check out if you do anything with complex interfaces. - Ben.

Supporting Your Support Team

The GiveWP Support Manual

Anyone who has a product based business (or SAAS) knows how hard it is to offer good, consistent, customer support. I’m sure we all try our best, but sometimes it’s good to have rules that help us maintain consistent quality.

GiveWP, a WordPress donation plugin, have opened up their support handbook and it’s a great example to learn from. - Ben.

Quick Links

" Make the best product. "
- Yvon Chouinard
Facebook
Twitter
MasterWP Website
Email
Copyright © 2018 MasterWP Weekly, a Pro Theme Design and Ellipsis Marketing LTD collaboration, All rights reserved.


Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.