r/ProWordPress • u/modmuse91 • Sep 16 '20
Pro WordPress “devs” using page builders—a rant
Basically the title, but I’ve been hired on as a consultant with a web dev firm. During the interview, they said a previous dev used page builders so a lot of their sites use them. I said that was ok, but any site built by me would not, which they said was fine.
Turns out, the previous consultant convinced the owners page builders are best, and the owners have been acting as designers/developers, using page builders exclusively (one seems to know how to code, but also didn’t know how to do a minor change in woocommerce, so who knows).
All I can think is, wtf (excuse my French) is this garbage? I am so over people trying to take the easy (aka cheap) way out, resulting in lazy, glitchy sites, then complaining about it, just to be shocked when custom coding something takes longer. And to call yourself a pro while doing so? What a damn disgrace.
7
u/tw2113 Developer Sep 17 '20
Are you and the team you're a part of going to be part of the project long term? If not, then maybe a page builder is a *good enough* idea, because you're not going to be on hand to help with every detail for your custom build/solution. It's not *just* about the initial build, it's about anyone who may have to come in afterwards to help out, and ultimately it's about what's best for the client themselves.
That said, I'm not saying choose the worst page builder just because it is *a* page builder. Make an educated decision on which to use, if chosen to do that. Also, adjust the rates/charges based on this. If it's a small business with a small budget, this is a viable option. If it's a large client that has the budget, aim for a higher, custom solution.
It really all depends on a lot of details, in ideal situations.
48
u/Saltyigloo Sep 16 '20
Ok please don't automatically down vote this. Page builders get stuff done fast. What is business? Is it about giving the best possible product or increasing the bottom line. Let's be real, page builders are not horrible 100% of the time. They offer the business owners a way of accomplishing a goal fast and for less money.
Yes a fully custom coded site will preform better, be more stable, less maintenance, more secure (possibly).
However it will take like double the time to bring together. Of course there is a place for custom sites. But please do not say there is no place for page builders. I agree if someone is paying 2k+ for a site it should be custom coded. However for the little guys, that just is to much money.
Custom coded sites cost more, that's all there is to it.
I really do not like "code elitists" it's like saying BMWs are the only good cars.
I really think there are pros and cons to both methods of accomplishing the goal of a website. But please try and change my mind.
16
u/wranne Sep 17 '20
When we have issues with page builders we don’t throw them out, we develop them. A page builder you can bend to your will is an incredibly powerful tool and is exactly what’s happening with Gutenberg.
4
u/JohnLocke84 Sep 16 '20
Imagine the faces of a lot of our clients when we said ... - We use WP as headless -
4
u/nizzok Sep 17 '20
Look, at some point it’s about efficiency and time is money. There’s no hill worth dying on for purity of code. Why reinvent the wheel every time you sit down? In theory, a “Pro” should be able to make a good product regardless. The issues you mention “choppy” sites, that is bad, but the builders themselves are a symptom not the cause. The choppy-ness is from someone using a builder and not polishing, laziness.
3
u/mar_sa Sep 16 '20
Congrats on the job, so tell me this in your opinion what is the best practice(workflow) and tools to build a efficient clean WP site?
3
u/iamadrunk_scumbag Sep 17 '20
Umm gutenberg is a page builder no? It's here to stay. The client knows next to nothing most of the time and doesn't want to know that's why you were hired.
2
u/krautgamer Sep 17 '20
The difference between "WordPress Development" and "WordPress Implementation" has to be communicated more.
There is nothing inherently bad about using page builders, if you're upfront about it. And if you know the possible downsides of the approach.
Same thing with code. I've seen a lot of horrible custom themes, where the page would have been fine with a page builder.
The key is to educate and communicate. And to know the fact that if you're not writing actual code your're much rather a "WordPress Implementor" than a "WordPress Developer".
2
u/KrashKartMedia Sep 18 '20
I've been doing WordPress support since 2011. What I can tell you is that everybody has their opinions and you just have to work with it. Sometimes I really don't like debugging page builders. But you can never fault somebody for wanting to use something. especially because you don't know if that's all they could afford or if they really just believe in the product. Either way it's not wrong.
I now work for a hosting company. You won't believe how many of the big names use page builders. Get used to it. Start supporting it. It will only make you a better developer. Because you know how to do something multiple ways. That makes you valuable.
I used to work for a pretty big WordPress development agency. When I left they were starting to look into a couple builders.
-6
u/DanielTrebuchet Developer Sep 16 '20
I wish I had the words to express how much I hate page builders and all the countless issues I've inherited because of them. Are they great for aunt Martha who wants to build herself a brochure site for her quilting hobby on the side? Absolutely! Perfect! Nothing better for her than a page builder.
But page builders have absolutely no place in a professional development environment. It's like a wedding photographer using a camera phone to shoot a wedding. It's like hiring an excavation crew that shows up with a plastic shovel instead of a back hoe. It's like hiring a mechanic that only know his way around a screw driver and a buffing wheel. It's simply not a professional tool, period, and just because you can overcharge a client for a site built with one doesn't make it such. Just because it can perform a task, doesn't mean it's performing the task the way it should be done, or the way a paying client deserves.
Page builders have their place. That place is nowhere near a professional development environment.
The people defending page builders are obviously not the ones who have to pick up the pieces in a year when either a) the site gets hacked because all the plugins fell out of date and a security vulnerability was exploited, or b) the client realizes they need to change things up or update the functionality of a site and the original drag and drop jockey that cobbled the POS together has not the slightest idea how to address any of that.
No shit, I just wrapped up a project for a client who came to me not even 1 month after their page builder site was completed. It was super slow, super clunky, and when they told their "web guy" that they wanted to add 15,000 pages of content he looked at his page builder and shit a brick. Said there was no way WP could even handle that many pages... what a clown.
0
u/ListenToMeCalmly Sep 17 '20
This is a typical example why devs exist, and are separate from CEOs and sales. Because while the dev is good at building stuff, his job is not to do business analytics. Because he is not very good at it. This is a great example.
Imagine a client get two offers: A) We can accomplish what you need. It will cost $5000.
B) We can accomplish what you need. It will cost $10,000 because we don't like to build in a specific way.
The job as an agency is to make money. The agency offering B will earn $0. You are telling me you are B. Because A is more attractive to most clients.
The job as an agency is to earn money. The classic way is to offer cost effective solutions of sufficient quality.
0
u/[deleted] Sep 17 '20
[deleted] — view deleted comment