As a Thesis/Focus user, I appreciate Chris's clear analysis of WordPress's core problems. His vision for an intuitive, modular platform without bloat is exactly what's needed. Given his track record with Thesis and Focus, I'm excited to see how this new platform transforms website building.
At first I was very much against Gutenberg. Then I learned about Reusable Blocks and decided to start making themes for it. I developed a few. Then I noticed that Gutenberg simply started changing the classes for standard blocks. Something that had a specific class before, now had a different class. This lead to me having to update my themes with the new class names. But existing content used the old class names. Thus some of my CSS code started doubling in size. Long story short, Gutenberg is now in the trash can. Classic Editor + ACF Pro is the best way to build WordPress websites at the agency level.
"Thus some of my CSS code started doubling in size." - Man, that is laughably bad! But as I suggested in the video, this is what happens without proper planning and execution. Software is not easy!
Here is a big realization I had after a few years of trying to develop themes and plugins for Wordpress. Initial I wanted to work with Wordpress because it seems easy to design and hand off the product to the client (so they are able to edit and create new content) The client will rarely edit the site themselves, and will be overwhelmed with all the options for submitting content. My realization? Just use a tool that is easy for you (even if that is just vanilla HTML CSS) then create hyper specific forms that are tailored to their content types for them to submit new content.
Excited for this. Been a Thesis user for a long time. I’ve used almost everything Chris has built, always top notch and user friendly. Looking forward to the next update 🙏
Interesting, and you have only scratched the surface. I’m sure you have heard of Etch? While your word processor approach is one way, many of us are looking for something in the page builder approach that pivots back to a workflow using raw html and CSS. Maybe there will be something in your platform/framework that will accommodate both? Interesting times ahead.
If the Page Builder approach is going to work, it's going to need to be completely separated from the UI where normal people compose content. Anything else is a conflation of structure and style, which is a violation of basic system design tenets.
I also want to point out that YOU are looking for a "page builder approach"... but you're a developer/agency. End users don't want or need that level of control/power in the place where they compose content. If you used Thesis, you would understand why Page Builders never needed to exist in the first place. (But I grant that *something* other than WP's joke of a "template system" was certainly necessary to bring about new efficiencies in website production. This is why Thesis exists as it does now.)
Most people think that the queenbee rules the workerbees. The truth is that when the workerbees aren't happy with their queenbee, they just replace her with a new one. I think the time has come to replace the "queenbee". We need a mature leader not this spoiled child.
You mention a lot about the user interface part, but the backend code and api is horrid. I've developed a few plugins for clients and to get a simple pull for Facebook data from a page took over 3k lines of code. You have to build a lot of stuff yourself, meanwhile something like react it can be done in less than 100 lines of code. Wordpress is antiquated 2005 junk, run by a man child.
I have another video where I reveal the problems with the Plugin code (API) and also show what could have been! Based on your comment, you'll appreciate it: ua-cam.com/video/G3VmNhRKzTE/v-deo.html
Saying that funcional is spaghetti code and object oriented prevents that is the greatest software joke I heard this year so far 😂 This guys need to have a deep look at some of the java trash rolling around the internet
I'm not sure what "surprise" you're talking about, as there are no surprises here. It's simply me showing the world the very clear problems with WordPress that can only be solved by moving to an entirely new platform.
I think it's not the spaghetti code that ruins your experience, it's 20years of designs and wide echo system around it, if you change something %20 of plugins won't work. I'm sure there are many much better alternatives and wonder why wouldn't you check them?
As a Thesis/Focus user, I appreciate Chris's clear analysis of WordPress's core problems. His vision for an intuitive, modular platform without bloat is exactly what's needed. Given his track record with Thesis and Focus, I'm excited to see how this new platform transforms website building.
At first I was very much against Gutenberg.
Then I learned about Reusable Blocks and decided to start making themes for it. I developed a few.
Then I noticed that Gutenberg simply started changing the classes for standard blocks. Something that had a specific class before, now had a different class.
This lead to me having to update my themes with the new class names. But existing content used the old class names. Thus some of my CSS code started doubling in size.
Long story short, Gutenberg is now in the trash can. Classic Editor + ACF Pro is the best way to build WordPress websites at the agency level.
"Thus some of my CSS code started doubling in size." - Man, that is laughably bad! But as I suggested in the video, this is what happens without proper planning and execution. Software is not easy!
I've never used Gutenberg. It's horrible.
Here is a big realization I had after a few years of trying to develop themes and plugins for Wordpress.
Initial I wanted to work with Wordpress because it seems easy to design and hand off the product to the client (so they are able to edit and create new content)
The client will rarely edit the site themselves, and will be overwhelmed with all the options for submitting content. My realization? Just use a tool that is easy for you (even if that is just vanilla HTML CSS) then create hyper specific forms that are tailored to their content types for them to submit new content.
Excited for this. Been a Thesis user for a long time. I’ve used almost everything Chris has built, always top notch and user friendly. Looking forward to the next update 🙏
There are few things I love more than seeing Pearson’s hair on fire with creative passion. LFG!
Chris - glad to see this!
Interesting, and you have only scratched the surface. I’m sure you have heard of Etch? While your word processor approach is one way, many of us are looking for something in the page builder approach that pivots back to a workflow using raw html and CSS. Maybe there will be something in your platform/framework that will accommodate both? Interesting times ahead.
If the Page Builder approach is going to work, it's going to need to be completely separated from the UI where normal people compose content. Anything else is a conflation of structure and style, which is a violation of basic system design tenets.
I also want to point out that YOU are looking for a "page builder approach"... but you're a developer/agency. End users don't want or need that level of control/power in the place where they compose content.
If you used Thesis, you would understand why Page Builders never needed to exist in the first place. (But I grant that *something* other than WP's joke of a "template system" was certainly necessary to bring about new efficiencies in website production. This is why Thesis exists as it does now.)
I see…
This is getting really interesting. I am waiting to jump.
Most people think that the queenbee rules the workerbees. The truth is that when the workerbees aren't happy with their queenbee, they just replace her with a new one. I think the time has come to replace the "queenbee". We need a mature leader not this spoiled child.
I'll go one step further-I think the platform should be so solid and flexible that it ends up not really needing a leader at all.
You mention a lot about the user interface part, but the backend code and api is horrid. I've developed a few plugins for clients and to get a simple pull for Facebook data from a page took over 3k lines of code. You have to build a lot of stuff yourself, meanwhile something like react it can be done in less than 100 lines of code. Wordpress is antiquated 2005 junk, run by a man child.
I have another video where I reveal the problems with the Plugin code (API) and also show what could have been! Based on your comment, you'll appreciate it: ua-cam.com/video/G3VmNhRKzTE/v-deo.html
"He's right, you know..."
Saying that funcional is spaghetti code and object oriented prevents that is the greatest software joke I heard this year so far 😂
This guys need to have a deep look at some of the java trash rolling around the internet
I can tell you don't know much about development. Pay close attention to my channel-it'll help!
@TheRealPearsonified 😂
I worked for a web agency between 2005-2013. I dont get yourvsurprise at all lmao. Great video regardless.
I'm not sure what "surprise" you're talking about, as there are no surprises here. It's simply me showing the world the very clear problems with WordPress that can only be solved by moving to an entirely new platform.
I think it's not the spaghetti code that ruins your experience, it's 20years of designs and wide echo system around it, if you change something %20 of plugins won't work.
I'm sure there are many much better alternatives and wonder why wouldn't you check them?
There are not "many much better alternatives." Not even close. But in the not too distant future, there will at least be one alternative.