The WP Minute - WordPress news Matt Report & Matt Medeiros

I really enjoyed the conversation lead by Brian Coords on the topic of version control for WordPress developers and builders.
He was joined by my recurring cohost, Mark Szymanski, as he asked the tough questions many beginners might be facing in their early development days.
Yes, that’s the same Mark that cohosted the episode of Crossroads of WordPress with me last week on the WP Minute+.
This post isn’t just about the advantages of using version control on your next WordPress project, but more of an example of how great the WordPress community is.
Mark and I have talked about building and learning in public before, and that’s exactly what Brian’s livestream was. A veteran WordPress developer, sharing his experience and teaching someone coming up in web agency world.
It’s fascinating watching Mark learn in public. I applaud him for having the humility to put himself out there in an effort to become a better agency owner.
Earlier in the year I predicted that we’d see more Mark’s coming on to the scene.
Tools like Elementor and Bricks have onboarded more enterprising individuals over the last few years to kickstart their own web services business. Most of them, like Mark, never had to crack open a code editor or SSH into a server and reboot the MySQL service when it ran out of memory.
Being able to rapidly build websites with a turnkey plugin can be a blessing and a curse. The theme of Brian’s livestream was partly to highlight some of the weak links in the chain when delivering client websites. Certainly “version control” isn’t the answer to everything, but it’s a trait that you’ll see in more mature projects.
So when do you actually invest in “version control?” It depends, and it might not be how and when you think.
If we put the technical term aside for a moment: Let’s think accountability instead. Explore what your client relationship looks like. How much are they paying you, how mission-critical is the website, and who is on the hook for support?
Themes, plugins, tutorials, free code snippets, all at our fingertips. It’s easy to pull something off the shelf and shove it into WordPress as a solution for clients. No one is the wiser. Until that off the shelf thing breaks, lacks a feature, or gets abandoned.
Say you delivered a $25k project to a client, but you built the entire thing on Cwicly, then it closed. Now what? Or you were using SearchWP on bunch of non-profit sites, then it was acquired by Awesome Motive and the license fee doubled — with lots more upsells to other products. Now what?
Now let’s talk communication: Novices might not mention they are using a page builder when they are quoting a client. “My God, what happens if they find out I paid $59 for a plugin that they could use themselves to build this site?!” I sympathize with that imposter syndrome, years ago I felt the same way.
Flip the script!
Instead you communicate in full transparency with the customer “Hey, based on your budget, I’ll have to build this site with a page builder tool. It gets us 90% of the way there faster and cheaper, but also has some limitations. You’ll save some money on the services side, but you’ll have to purchase a license in order for us to use on it on your site. If we had a bigger budget or more time, we could get exactly what you want with a custom theme.”
It’s Spring in the US so I’ll use this other analogy with my desire to erect a shed in my yard: Do I build it myself? Nope. Do I buy a prebuilt one from Home Depot, and worry about the quality versus cost spent? Or do I hire a builder, knowing it will last longer, be exactly what I want, but cost 3x more?
Open communication will always work best with clients, especially when you want to set clear boundaries of accountability.
There’s always a balance. Obviously, version control isn’t the answer to this, but it is part of an overall solution where more mature agencies will measure the risk when putting a project b

The Biggest WordPress Moves While Mullenweg was on Sabbatical 

Matt Mullenweg is returning from his 3 month sabbatical, dubbed “Samattical”, which kicked off February 1, 2024. 

He handed the CEO reigns back to Toni Schneider and placed Daniel Bachhuber in charge of WordPress.com in his absence. I thought we’d see the whole organization coast while the open source benevolent dictator dug his toes into the sand, but Automattic/WordPress stayed as busy as ever!

I don’t know how much Mullenweg was involved with all of these milestones — something tells me he didn’t stay as disconnected as he had hoped. Let’s take a look at some of the big moves that happened with WordPress, Automattic, and the community while Matt was away. 

1. The WP Tavern Hunger Games
One of the first major activities to kick off was the search for two new full-time writers to breathe life back into WP Tavern. It was a Hunger Games-esque approach, where 7 or 8 writers, duked it out to be crowned winner #1 & #2. 

Author Brian Coords was the last contestant to publish a post on March 14th, 2024. There hasn’t been any clear announcement on who earned the position or what happens next, and most authors I’ve spoken to are still wondering what’s next for their writing careers at the Tavern. 

2. Woo.com → WooCommerce.com
Something I didn’t have on my Bingo Card was the short-lived woo.com domain defaulting back to the original WooCommerce.com domain. 

“Moving to Woo.com created challenges for our users to find WooCommerce in Google searches, which were made worse following Google’s March update. To address those challenges, we assembled a group of SEO experts and consultants to evaluate the best way to build on the strength of the WooCommerce brand.” Kevin Bates wrote in an update.

3. The Old WP-Admin Dashboard is New for WordPress.com
In another, what’s old is new again, WordPress.com is giving users the ability to “roll back” to a traditional WP Admin interface. It seems there’s no future for the once innovative Calypso project, citing that developers were looking for a more familiar interface when working on WordPress.com sites. 

This might be a sign that more WordPress consultants are starting to recommend .com more to their customers now that the platform has been supporting user installed plugins on the $30/mo+ plans. 

4. Automattic spends an additional $125 Million on Messaging with Beeper Acquisition 
Automattic is pouring money into messaging, with its latest acquisition of Beeper. Which I’m assuming Mullenweg was quite active on during sabbatical. 

I like the idea of Automattic building up a strong solution for messaging. In a world where SEO is getting squeezed and social media feeds being curated by ad-driven algos, we need more direct channels with our readers/subscribers/customers — and I think that’s direct messaging.

It could be an exciting new frontier with Automattic leading the charge, and I’m here for it!

WordPress Studio: The Future of Local Development?

5. WordPress.com Launches Studio App
The new Studio app allows users to run WordPress installs, locally on their computer. 

This is a great way to learn WordPress and develop WordPress sites for free. It’s powered by the same technology that runs the official WordPress playground and gives users the ability to publish their local websites to a temporary WordPress.com account to share with the world. Other hosting platforms like WP Engine and Kinsta offer local development environments making this a natural fit for Automattic to offer.

6. Big Sky: WordPress.com starts waiting list for AI designed websites
WordPress.com decided to throw their hat into the AI web design ring by opening a beta signup for their latest project, BigSky

I’ve signed up to trial the product, but I also signed up for access to Studio before it was released and didn’t hear anything — fingers crossed. If anyone at Automattic is reading this: I

WordPress is amazing not just because it’s a great tool to publish words on the internet, but that it has the potential to encourage you to learn more about the web — if you want. 

If you remember the golden age of automobiles, enthusiasts would change their own oil or make the repairs themselves to avoid bringing them to the dealership. An act to save a few bucks or just because you loved the idea of doing the work yourself. Back then, cars weren’t powered by computer chips or electric motors — they were mechanically pure — this was your rig. 

You rolled up your sleeves, got out your toolbox, and slid under the chassis of your daily driver. Not only were you learning how cars were built, you were extending that knowledge to work on other cars as well. Industry knowledge that lead folks to have a career in automobiles, wherever that took them.

There was a whole economy of DIY auto mechanics — a whole industry, really. 

Chilton Books used to publish guides for the DIYers which included detailed diagrams of the cars they were repair until the internet accompanied by the production of more complex cars laid waste to their business. Breaking apart a car to learn how it worked just wasn’t feasible anymore. 

You could even draw the parallels of open source WordPress to the likes of a closed source Webflow, for instance. 

Sure, you can learn how to build and design website with Webflow — in fact you kinda need to know how to before you dive in — but that mechanical purity is what’s missing. 

In other words, you can’t dismantel Webflow and see how it’s doing its thing, but you can with WordPress. You can’t bring closed source systems to a different hosting server and reconfigure the stack to get it dialed-in for optimum performance or to change where you store your data — you can with WordPress. 

The big debate happening right now is understanding who WordPress is for. What kind of software are we building? It’s certainly trending towards a more competent website builder for the everyday user, but I also think it’s ushering in a new type of developer class as well. 

Developers are finicky. They are mostly stuck in their ways, have their preferred toolset, and come equipped with strong opinions. Artists in the very sense. 

Your typical development stack for WordPress, along with the definition, has been challenged over the last 5 years as page builders became more nascent. If you’re not cracking open Notepad++ to change your theme, are you even a developer? 

Advancements in the Site Editor and the Gutenberg project aside, Automattic has been quietly changing the way people can get started with WordPress faster than ever before thanks to Playground and the recently launched Studio app. 

Now to the point of the article: This is how WordPress is helping beginner developers.

With Playground, you can export the site you build right in the browser as a ZIP download. Want to try a new feature that is only in GitHub and not committed to the release? Pull it from Github and try it out. Studio lets you run multiple WordPress installs locally on your Mac (Windows soon) along with a full filesystem to interact with. Want to share your customized site with someone? They’ll give you temporary hosting on WordPress.com to share the site you built. 

This onboarding into WordPress is lightyears ahead of where we were in the past. Even if you’re a curmodgeoned developer stuck in your ways, you must admit, it’s never been faster to start exploring WordPress than it is today. 

I haven’t even told you about the Block Theme Builder plugin, which allow you to design an entire theme inside your WordPress install, allowing you to package it all up into a nice distributable WordPress theme. 

I love software that makes me feel powerful. A power user, that isn’t quite a full-blown developer, but I can see the other side of the fence and I want to get there.

This is what I love about Word

I recently had the pleasure of meeting Sam Harrison, a professional Webflow consultant and content creator. 

He was open to co-host a WordPress vs Webflow debate with me, while also unpacking how business is going for his services company. Heading into the debate, I spent a a few hours watching his content and really enjoyed his Webflow Components Basics + How to Start a Web Design Business. So why did I invite Sam on? 

Page Builders, especially Bricks, has been the topic du jour of late.

That crowd really wants WordPress to have much more power inside the editor — and I totally get it. These powerful 3rd party tools can be really attractive, and if you haven’t been in the WordPress space for the last 20 years, you start to wonder why our favorite CMS is lacking these features. 

Bricks is often framed as the tool that brings a Webflow experience inside WordPress — all the powerful design and page building tools you could want, surely. I’ve had some conversations with prominent WordPress agencies now offering Webflow as an alternative solution to WordPress. 

It all makes sense…But the choice shouldn’t start at which tool to use, but whether or not you want open source software or a commercial solution for your project.

To simplify: do you care that you have the benefits of open source WordPress (along with the baggage) or does having a single turnkey app provide the best solution? Now how does that play out if you’re selling services to clients?

Sam and I played a little game where we placed the winning cards of particular features of the competing platforms in their respective columns. 

I’ll admit, the odds were stacked against Sam (and Webflow) seeing that he was on my podcast, but WordPress comes out the winner in most areas, so long as you’re siding with the advantages of open source. The ecosystem, the community, the ability to customize the platform — it’s a hard sell to get me to use Webflow. 

That doesn’t mean we can’t learn from Webflow and their users. Let’s face it, it’s not a fluke that they’ve been successful for this long.

Having a comprehensive toolset to design pages makes a lot of sense. Also not having to worry about updates, hosting, and 3rd party software conflicts sounds like a dream that Webflow users get to live everyday. 

Though I noticed that in this short time of exploring Webflow, WordPress isn’t massively behind, pound for pound. And I’m talking specifically just core, not even when you decide to bring in plugins like ACF or Gravity Forms. 

If you like the design tools and interface of Webflow, mixed with their new Components libraries — the gap in WordPress isn’t all that wide. 

However, when you look at something like the writing experience — specifically blogging or posts in general — Webflow isn’t even competing in the same league. Sorry, Sam. 

I guess what I’m saying is, as much as we can learn from the UI/UX and passionate community of Webflow — their team could also learn from WordPress. Heck, Gutenberg is an open source project, even Drupal has a fork. Maybe Webflow could improve their content editor with…Gutenberg? Go open source! 

Let me know what you think! 
Watch the WordPress vs Webflow video: https://www.youtube.com/live/p82lLK56XOE?si=2_1zuEPsKHI7aft7


★ Support this podcast ★

Read the full show notes here


★ Support this podcast ★

Read all the shownotes and get the links here


★ Support this podcast ★