New Video Explores Site Building Progress From WordPress 5.0 to 6.0

Do you remember what it was like to use WordPress 5.0? Three years and ten major releases have radically changed the site building experience, but it’s not always easy to see recognize when focused on some of the smaller, iterative changes that slowly add up. Anne McCarthy, WordPress product liaison at Automattic and co-release coordinator for 6.0, has created a short 13-minute video that shows the immense amount of progress contributors have made on site building features.

McCarthy takes viewers back in time to WordPress 5.0, released in December 2018, which introduced the block editor and the Twenty Nineteen default theme through the work of 400+ contributors. She demonstrates using the Customizer with the default theme. These were simpler days and it’s clear now how limited the Customizer was for implementing the most basic changes.

The video contrasts that experience with the upcoming 6.0 release, which features the work of 500+ contributors on features that didn’t exist three years ago.

McCarthy quickly demonstrates the 6.0 site editing experience, swapping out template parts, and showcasing the breadth of the customization available for images, colors, typography, controlling the posts that are displayed, style variations, and the impressive array of design tools available.

Ten major versions later, nearly every aspect of a WordPress site is customizable through the site editor. For those who have not yet made the leap into full-site editing – it’s essentially like the old Customizer but with super powers, better instant previews, and the interface is a panel on the right. At this point, I don’t think the usability is at a level where someone can just get in there and immediately know what they are doing. It takes a little bit of exploring, but it’s moving in the right direction.

Videos like this one show what is possible and just how far WordPress has come since it first introduced the block editor. It also indirectly answers Joost de Valk’s recent claims that the full-site editing project not being done yet is partially to blame for WordPress’ recent decline in market share.

While WordPress remains the uncontested market leader among CMS’s, some say this small percentage of a decline is inconsequential. Matt Mullenweg has stated in previous interviews that he views market share stats as a “trailing indicator” in the quest to create the best possible experience for users and developers. A growing market share, in that sense, is a signal of user satisfaction.

WordPress jumped into the block paradigm at the right time, just as many other apps began adopting the concept of composable blocks for creating content and designs. Full-site editing is the extension of that vision but it takes time to make it something polished and delightful to use. McCarthy’s video is a good reminder of the limitations that users previously labored under while trying to edit their sites, and the “why” behind all the effort going into FSE.

“As someone who’s currently on the WordPress 6.0 Release Team, I can attest that the project needs more contributors,” WordPress contributor Nick Diego said in response to the recent market share discussion. “The fact that FSE has taken so long is not a lack of effort. There are many contributors pouring their hearts and souls into the project. We just need more help.”

5

5 responses to “New Video Explores Site Building Progress From WordPress 5.0 to 6.0”

  1. There’s no denying progress has been made but this needs to be taken in context: 6.0 is about 4 steps forward from the 10 steps backwards in reliability that was introduced by 5.0.

  2. Super excited about the future of WordPress. I’m still using the classic editor on all my sites, but may start using the block editor in the near future.

  3. I think a lot of developers are wary of building on shifting sands. Once bitten, twice shy. The project is unreliable in that new surprises and demands are made on site creators with every release.

    An example situation: A client wants me to specify a corporate site for them, it is to be edited and maintained by their interns. I must cost it and give a timeline, and provide training docs on how to edit (at a level an unskilled new employee might understand)

    How do I prevent the editors from adding weird backgrounds, filtered pictures, etc! I lock it down, I must include my boilerplate which locks and hides the effects, most of the blocks, the WP pattern library, the patterns (because the implementation changes so often its a massive workload to support), and as for FSE … no client wants this, so now I have 80 more things to try and discover the way to turn them off.

    So that’s corporate clients, but what about small business , one person selling from home and maintaining their own site?

    In my experience with those clients they start off excited to drag and drop a site design, tantalised by ads and chafed by the cost of hiring a webdev. These sites end up a total mess and I’m asked to “make it really simple, just get rid of everything, just make it black and white”.

    Because these single traders are not designers, and do not have the time or inclination to learn about layout, colour theory, never mind about topics such as SEO.

    The developers of WP gutenberg and FSE are working hard, but I cant see the benefits to any client. And if I develop for it then the burden is on me to support clients in every change to the implementation.

    • @Steve
      I can see how this can be a nightmare. Is there a reason that training and workflow won’t solve these issues? We use staging sites and a workflow with approval to have changes propagated to the main site. The main site is 99% locked down.

      Any mistake happens on the staging sites and just opens the door to more training when mistakes happen.

      You could also use adminify or similar plugin.

  4. Just wanted to say thank you for doing a write up on this video. It was more rushed than I wanted it to be with my role with 6.0 but I hoped it would serve to inspire and remind us how far we’ve come, without taking away from how far we still have to go.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Newsletter

Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: