Page builders might not be a good idea

&gt; I don’t want to offend anyone here, but building pages is more than just writing content and placing it somewhere on the page. You should leave this job to a professional, especially if you want to maintain the site on a longer run.<p>But this use case of simply getting some content accessible on the web is the primary reason why page builders are so popular :)<p>For example, a large number small of businesses just want simple page displaying their working hours and some pictures of inventory. If you go to a &quot;professional development agency&quot; and ask them to build you a site with just these features, you will get a quote for 200 thousand dollars upwards (speaking from experience). With page builders, you can get your nephew to build you a site during school off-season and it will be infinetly better than having no site at all and still probably do the job well enough as a professionally built one.<p>I get that the original post is basically a sales pitch, but there is huge value to be had from page builders and it&#x27;s dishonest not to mention it.

I think the article misses the point that people just want to get things done. Particularly this point is so naive:<p>&gt; using a page builder doesn’t make you a developer.<p>People who are using page builders are not doing to pass the arbitrary qualifications of being a developer. They just want to get something done and getting a developer to create a performant page is just so much more expensive. Even within big companies some departments leverage these because getting developer bandwidth is just too expensive for most of these use cases.

I find this whole thing thoroughly unconvincing. Page builders provide enormous value for a modest price. If you run into an insurmountable problem with one, you could rebuild your whole site on a different platform (including manually copying over all the content), and then do that again a few more times, and still spend far less than you would having an agency develop a bespoke site with the latest trendy tech that will be obsolete next month anyway.<p>The fraction of businesses that need something really custom&#x2F;special is vanishingly small. And the fraction of businesses that need a pixel-perfect design and consistency across all their pages is tiny, too. Your customers don&#x27;t care about that crap nearly as much as you do. Just keep it simple and make the information they&#x27;re looking for easy to find.<p>I&#x27;m a software engineer. I love building stuff. I can make kick-ass web stuff if called upon to do so. But please, don&#x27;t waste your money paying me to build something you don&#x27;t need.

There are many things that can be done better by experts.<p>But to double the quality, you multiply by 10 the cost.<p>E.G: I wanted to start writing again. I had an idea for the entire structure of the site, and pretty neat features I only could get if I coded it myself.<p>Then I started to feel like writing, so I wrote. As usual, it took hours, then I had to go back to my life.<p>I was now left with the choice of not publishing for months, and being frustrated in the writing process, or just use a ready-made platform.<p>I chose the latter. I went to substack. And publish the first of the 3 articles I already wrote. Next week, I will be able to publish the next ones, and write more.<p>Because it turns out I want to write and publish more than I want to code a publication platform. No matter how awesome the platform was going to be in my head.<p>So page builder are a very good idea. Because we don&#x27;t live in a universe without constraints, and most humanity has to make Pareto choices.<p>It&#x27;s just a trade off, as usual in IT.

&gt;I am referring to the WordPress and Shopify ecosystems here<p>&gt;The content is not reusable (you cannot reuse content on other pages)<p>Not sure I understand this. Platforms like WordPress certainly have widgets, reusable blocks, shared headers&#x2F;footers, and so on.

&gt; The content is not reusable (you cannot reuse content on other pages). &gt; The design is not consistent (pages often don’t look the same). &gt; The site is not maintainable (change on one page doesn’t propagate to other pages). &gt; The content is not maintainable (the content cannot be easily extracted from the database). &gt; The site is not very performant (page builders load a lot of extra assets).<p>All the above depends on the tool that&#x27;s used. I&#x27;ve set up many sites that had page builder features but didn&#x27;t have these drawbacks. Certainly there&#x27;s many other tools out there. What OP seems to be talking about are page builders that output and store raw html.<p>&gt; There’s always a missing feature (page builders cannot solve all your problems).<p>True, but that goes for literally anything you can use to build websites, all the way down to the HTML spec. And extending the page builder is often possible with professional help.<p>&gt; Getting to know page builder doesn’t make you a developer (leave the job to a professional).<p>Developers are not by definition a professional in all aspects of page creation. A user well versed in, say, WordPress, will know about the drawbacks as well, and know how to mitigate them.<p>I&#x27;m not a big fan of page builders myself, but there&#x27;s a place and time for these tools. I&#x27;m currently working with a team to implement a 1.000 page website in contentful and react, based on similar thinking as OP. It&#x27;s an absolute shit show and it feels like being the hostage of &#x27;professional developers&#x27;.<p>In the end the most important is to choose the right tool for the job, and there&#x27;s a place for these page builders.

Page builders are only seen as bad ideas when you have better ideas to choose from. In most cases, hiring a professional is not a viable alternative to doing it yourself.<p>And since none of the problems presented here are new or unique to sites built with page builders, it follows that the others ideas don’t actually solves them.

The advantages out weigh the disadvantages. There are more layman than professionals. And worse yet profs are taking longer and longer to build simple websites.

Hello, founder and CTO of www.shopstory.app here. None if these arguments apply if you build page builder right. I believe we&#x27;re on the right path.<p>First, it works inside of headless CMSes. It means that you get all advantages of structured content and yet add sprinkles of unstructured content when you need on top of that. You can always connect structured data into visual blocks built with Shopstory.<p>As for design consistency we build everything around design tokens. Not only fonts and colors but also page margins, grid gaps etc. Also, you will soon have permission system where designers can build templates but editors can&#x27;t modify visual properties.<p>The bottom line is that I believe in the future we won&#x27;t need to make a tradeoff between visual vs structured. You can have both at the same time and just fine tune the system to whatever direction suits you better.

&gt; The design is not consistent (pages often don’t look the same).<p>I don’t think site-level consistency is as important or prevalent as you’d think.

It&#x27;s simple, page builders allow users to do it themselves and it allows the page builder platform to have high margins - they are CHEAP to run and entirely predictable.<p>The few page&#x2F;site builders that use dynamic data, such as Duda (in part) and Builder.io very much reflect the cost difference, from 10€ of standard page builders to 99€-449€&#x2F;mo for builder.io.<p>I&#x27;d say that there are builders that solve every one of his points, but they are very costly.

Almost none of the complaints are true of Webflow, FWIW. It&#x27;s by no means perfect, but there are many use cases where it is a much smarter decision than contracting or hiring a site engineer.<p>Sprinkle in some custom widgets as needed and you can get pretty far (albeit not with optimal page speed performance).

&gt; And that is the seventh problem: using a page builder doesn’t make you a developer. Developers and users don’t think alike. Developers’ brain works completely different, and it is always trying to solve problems in the most efficient way. Experienced developers predict and anticipate problems way before they emerge.<p>Someone should let the WP Core devs know, because the page builder SaaSes have been eating their lunch delivering on business website needs while Automattic lurches from one disaster to another with their &quot;dev-friendly&quot; Gutenberg full site editor.

I use page builders every day despite being able to code, I think they&#x27;re great but they all suffer from the same issue. The developers of the page builder tool need to decide what you can change and what you can&#x27;t, and it&#x27;s purely subjective. If you make absolutely everything editable you&#x27;ve just replaced editing CSS with a GUI (more or less Webflow) and you can&#x27;t hand over a complex UI to a non-dev. I don&#x27;t know how you solve this problem.

Replace the word &quot;Page&quot; with &quot;GUI&quot; and this could be an article about Visual Basic or HyperCard from thirty years ago.

Paying Web &quot;Designers&quot; Might Not Be a Good Idea. This is just a sign of their dwindling business.

Page builders and LLMs are the future. There was a time when that wouldn&#x27;t be as plausible, but the web is reverting back to being a place to dump text and media, and host restaurant menus, in which case it begs the question why we need so many web developers.

Looks like dark mode is broken under firefox, the top banner shows white text on a white background.<p><a href="https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;vlQQBDZ" rel="nofollow">https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;vlQQBDZ</a>

<p><pre><code> Getting to know page builder doesn’t make you a developer </code></pre> Yeah, well, that&#x27;s just, like, your opinion man

This is outdated and suppose you are writing yet another bad page builder. Most argument apply to any technology that do not make a proper use of a component based architecture, code generation or static rendering. For instance Plasmic is adamant to allow compatibility with modern framework such as Next.js and even has been a pioneer in the field of static personalization, a very performant approach.

I&#x27;ve long been building the contrary position. Our industry has taken massive steps backwards by not embracing content creation tools in our pipelines. Imagine if game devs insisted on art being hand crafted triangle by triangle?

Poorly written article with poorly written arguments. What this person doesn&#x27;t like is <i>bad</i> page builders, which is reasonable. But they seem completely unaware of what is possible in modern page builders.

This was written by ChatGPT, no?