Who is Full Site Editing For?

Episode 36 February 03, 2022 00:15:57
Who is Full Site Editing For?
WP Review
Who is Full Site Editing For?
/

Hosted By

Joe Casabona

Show Notes

When WordPress 5.0 and the block editor came out, though it was off to a rocky start, the value proposition was clear: THIS is a better experience for content creation than the Classic Editor. After all, that experience was largely unchanged for 15 years. But now that 5.9 is out, we need to ask: is the value proposition for Full Site Editing as clear?

Brought to you by GoDaddy Pro

Get all of the show notes, and a written to be read article over at https://wpreview.io/36

Show Notes

View Full Transcript

Episode Transcript

When WordPress 5.0 and the block editor came out, though it was off to a rocky start, the value proposition was clear. This is a better experience for content creation than the classic editor. After all, that experience was largely unchanged for 15 years. The detractors knew it too, though they didn't want to admit it. Many had switched to page builders instead. And when I asked how explaining shortcodes to clients was better than blocks, someone respond that it didn't matter because they would handle updates for their clients. My response - and make no mistake, I will die on this hill - is that making minor updates inside the WordPress editor for your clients is a terrible way to spend time in your business. The block editor makes that a lot easier. Like I said, the value proposition is clear. What might have a less clear value proposition today is another major feature that just came out with 5.9. And that's what we'll be talking about today. Welcome to WP Review. A show that provides analysis on what's happening in WordPress and what it means for users and business owners in the ecosystem. This podcast is brought to you by GoDaddy Pro. My name is Joe Casabona. And today, we're going to answer the question: Who is Full Site Editing For? So let's get back to updating client sites. Even if for some reason you wanted to spend all of your time making minor updates inside the WordPress editor for your clients, locking the site down so that your client can't break the site is an unreasonable thing to do. Imagine buying a car and then the dealer telling you that only someone from the dealership can drive the car. Or to a less extreme extent, imagine the dealer telling you that you're not allowed to make any change to the car from adding an air freshener to painting a racing stripe on the side of it. And sure the ladder might look terrible, especially if it's one of those big flames on the side of the car. But the point is that it's your car. You paid for it after all. And Toyota doesn't make its money by worrying If their clients are going to “ruin their work” which brings me to Full Site Editing. As a Web Developer for 20+ years and a site builder, since the first time I laid eyes on Beaver Builder back in 2015, I love the idea of Full Site Editing. You mean, I can make changes to templates without having to dig into the code? I can actually spend precious coding time solving real problems instead of slightly tweaking the loop to show a divider under the title. Sign me up. But recently I was in GoWP’s Digital Agency Owners’ Happiness Hour discussing WordPress 5.9. And Chris Lema posed a question: Who is Full Site Editing For? Now, I've got to admit I was taken back for a moment before realizing that I haven't thought for a single second about this question. And after taking a beat, I said, “Theme Developers.” And then Chris said, “Do Theme Developers need this?” So who is full site editing for? There's a really good post on [codejerk.com] called “The Complicated Futility of WordPress. And I'll link that in the show notes over at [wpreview.io/36]. If you work with WordPress and I'm guessing you do, I'd encourage you to read it. But here's a short excerpt from the article “The thought of client-side marketing interns ‘play(ing) around with site-wide designs’ should make the blood of any professional run cold. Sites that have been painstakingly designed and built, reviewed and refined to the last detail every step of the way with stakeholders on the client-side, optimizing UX, legibility, performance, and upholding the client’s brand can now be squelched in an instant by someone 3 months into their job who prefers yellow.” while slightly condescending. The point is well taken. But does it jive with what I just said above or earlier about not being able to customize or even drive your brand new car? And sure, adding a racing stripe is one thing. But imagine you wanted to replace the headlights with megaphones or make the engine look nicer by removing some of those exhaust pipes. Well, now your car doesn't work. Unless you know how to build cars, there's a natural limit to what you can reasonably do to your car. Should websites be the same? I think so. But this point lands within the realm of my answer to Chris. I don't think full site editing is for end-users. Is it for no-code site builders? On my live stream earlier this week, become a member over at [joincreatorcrew.com] to see the replay. I decided haphazardly to try to redesign a site with 2022 and Full Site editing. I had no plan. This was more of an exploratory redesign. And while I could do some of the things I wanted to an extent, there were strange limitations that come with the territory of a beta product. I don't think site builders can reasonably accomplish what they would need to with full site editing just yet. And I'll give you three reasons why. The first is that the UX is still pretty bad. If I wanted to build a custom page template and the incredible feature of full site editing, I need to create a new page, go to template, then click new. This functionality isn't anywhere in the site editor, which is confusing. Especially if we want to make full site editing and an all-inclusive experience for building out the design of a site. The second reason is that there are only two categories of template parts we can make - headers and footers. Now, this is absolutely a reasonable start. But we also have sidebars or widget areas, and navigation menus. And while there are blocks that can handle this, having a one-to-one mapping of the types of templates you can create in theme development is important. If you can register multiple sidebars, you should be able to create sidebar templates. The third is that there's no support for other devices. Set padding and layout on the desktop and hope for the best on mobile. This is coming, but it's not there yet. So site builders should still look for flexible themes like Kadence if they want to build a website with no code. That leaves theme developers. But before we talk about them, let's hear from our sponsor GoDaddy Pro. This episode is brought to you by GoDaddy Pro. GoDaddy Pro is an experience tailored specifically to the needs of web designers and developers and helps them more efficiently manage their work and deliver results for their clients. Combining website, client, and project management, GoDaddy Pro is an integrated solution made by and for web professionals. Whether you are new to web design or looking to grow your business, you'll find the tools, products, guidance, and support to help you deliver results for clients. At the heart of GoDaddy pro is the hub. From one intuitive dashboard, the hub seamlessly brings your sites, clients, and projects together. Manage and monitor all of your client's WordPress sites from a single place. No more juggling multiple client passwords. With one click, perform bulk updates, backups, and security checks no matter where your client's sites are hosted. You will save time and free up your day. Integrated Project Management makes it easier to keep track of your client communications and deliver projects on time. Electronically sign, notarize, and store documents. You can create a visual timeline to break down projects into smaller tasks, to stay on track, and on time. Access all of your client accounts with a single sign-on through their tailored shopping experience by-products to help clients grow their business like powerful e-commerce stores using Woocommerce. You can always reach dedicated and knowledgeable customer support. 24/7. On top of that, you'll find a thriving community of web designers and developers who share advice, insights, and learning opportunities. GoDaddy Pro is free to join. Head over to [go.me/wpreview] to get started. That's [go.me/wpreview]. The problem we run into here is that while full site editing, ostensibly makes theme development easier, again, it's not all the way there. There are still lots of limitations to it like the ones I just listed and a theme developer will need to cover those. So as a theme developer, you'll need to create styles for blocks to account for mobile layouts, perhaps bloat your CSS a bit and provide a ton of block patterns to help users who are relying on the site builder to carry the load. That's not to say that this is a bad beta. It's not. But it's front and center if you use a block theme. The customizer goes away unless a plugin requires it which means that this is not ready for prime time beta will become the de-facto way new users and new websites do things. And I don't want you to hear what I'm not saying. I'm really excited about Full Site Editing. But when I think of the wider WordPress ecosystem, I'm left wondering what Chris wondered on that Happiness hour call. Right now, who is full site editing for? in other words, full site editing is in core now. So who's using it now? That, I'm less sure about. I think we'll be a lot more sure when 6.0 comes out. And if that's the case, did we really need to turn every production WordPress site into a beta tester for full site editing? Will the returns be worth someone stumbling into the site editor and messing around with it because they've never seen it before? Are we putting undue stress on people who manage client sites? or is it fair to assume that most production sites aren't using a block theme so it doesn't matter much at all? Are only the savvy curious users trying out full site editing? My answer to the question: “Who will full Site Editing be for?” is “No Code Site Builders.” But that's not my answer today because you still need code or you need to use something else to supplement the full site editor. So until then, I will just continue to echo Chris's question: “Who is Full Site Editing for, today?” If you have an answer, I'd love to hear it either on Twitter (@jcasabona) or by filling out the contact form over at [wpreview.io]. Now, as we move into the recommendations portion of this show, I actually have two for you today. Gutenberg 12.5 is out. And that includes a lot of things that I just talked about in why full site editing's not ready for prime time. It doesn't include everything, but it makes a lot of improvements. So if you are full site editing curious, I recommend you check out 12.5 of the Gutenberg plugin. But I also want to tell you about a new project that I launched called “Creator Toolkits”. You can find those over at [creatorcourses.com/toolkit]. And these will help you find the right tools to make your personal and business life easier. I've been using WordPress for a long time. I've built all sorts of sites from learning management sites to big intranet sites, to podcast websites. And I've decided to take my knowledge and put together these free toolkits for people who might want to do the same thing. Each one recommends hosting a theme and helpful plugins. If you join the mailing list again over at [creatorcourses.com/toolkit], you’ll get a bonus podcast. So the way I'm billing it is you get the “WHAT” for free by visiting [creatorcourses.com/toolkits]. And you get the “WHY” by joining the mailing list. Why did I choose Learndash over LifterLMS? Why do I recommend certain hosting over another hosting? Why do I keep talking about Kadence Pro? And if you join Creator Crew pro, then coming later this year, there will be full tutorials on how to implement these toolkits. So get the “WHAT” for free, the “WHY” by joining the mailing list, and the “HOW” by becoming a Creator Crew Pro member. Again, that's over at [creatorcourses.com/toolkit]. And the toolkits are completely free. But that is it for this episode of the WP Review. I hope you liked it. I hope I'm creating good conversations. Sometimes it could sound like I'm being curmudgeonly when it comes to WordPress. But I've been using WordPress for a long time and I want to continue doing that. I want to help bring other perspectives into the WordPress space. That's my mission with WP Review. And I hope it's helping. So thanks so much. To get even more WordPress insights and to subscribe to this show, head on over to [wpreview.io/subscribe]. You can find all of the show notes over at [wpreview.io]. And if you liked this episode, share it with a friend. Maybe they're wondering who full site editing is for? Thanks so much to GoDaddy Pro for sponsoring this and every episode of WP Review. Until next time. I'm Joe Casabona and I'll see you out there.

Other Episodes

Episode 38

February 18, 2022 00:18:06
Episode Cover

Your Virtual Event is not a WordCamp

A topic that’s come up for me multiple times over the last six months iswhether or not speakers should be paid. I had a debate with Nathan Wrigley about it at the end of last year. That debate was based on an article I wrote back in October called, “We need to talk about speakers and virtual events.” But beyond paying speakers, we need to treat them with decency. We need to value their time and not treat them like they are just here to serve us and our cause. And that’s what we’re talking about today. Brought to you by GoDaddy Pro. Get all of the show notes, and a written to be read article over at https://wpreview.io/38 Show Notes We Need to Talk About Speakers and Virtual Events Faceoff: Should Speakers be Paid for Virtual Events with Nathan Wrigley Creator Toolkits ...

Listen

Episode 26

October 14, 2021 00:23:43
Episode Cover

Owning Our Own Platform and Responding to WordPress Hit Pieces

Last week’s Facebook outage brought an onslaught of platitudes from people talking about how terrible Facebook is, and how you should own your own platform. But even as a developer myself, my thoughts are a little different. Plus, how we should react to WordPress "hit pieces."   Brought to you by GoDaddy Pro   Links The Next Web Publishes Storyblok-Sponsored Hit Piece on WordPress (WP Tavern) Introducing Twenty Twenty-Two (Make.WordPress) Notion getting a "Page Builder?" (David Bisset) Do we REALLY Need to Own Our Platform? BlockMeister Page Builder Summit Join the Build Something Club ...

Listen

Episode 27

October 28, 2021 00:23:49
Episode Cover

What's Up with the Block Editor?

There's been a lot of news around Gutenberg and the block editor as we barrel towards the November 9th feature freeze. Plus, are we getting the whole story of why the block editor exists and what it's supposed to do?  Brought to you by GoDaddy Pro Get all of the show notes at https://wpreview.io/027 Get even more great content by joining the Build Something Club ...

Listen