Page Made with Gutenberg

You won’t believe how terrible the consequences are when you compose posts with the Gutenberg editor.

You see, the thing most people don’t realize is that Gutenberg isn’t free—it involves a considerable trade-off that would probably lead most people to abandon it if they had a clear idea of the consequences.

So let’s talk about those consequences…

The primary issue with Gutenberg is a conflation of substance (content) and style (the resulting design). This makes it incredibly challenging to operate over time, simply because every “block” within Gutenberg becomes a customization touchpoint that must be addressed in the future whenever your design changes.

This is no big deal if your design is never going to change and you never have to make any adjustments.

But how often have you found success in your endeavors when you refused to make changes over time?

It’s clear that agility and flexibility are important—if underappreciated—qualities you’ll want to honor if you want to run a successful website.

So let’s do it.

Let’s make a sample post with Gutenberg and then show people how Gutenberg pollutes their content databases to a degree that renders it useless over the long term.

Let’s show them the insane number of customization touchpoints they’ll have to address in the future.

Let’s make it clear they are compiling a MASSIVE to-do list that will force them to [1] take a TON of painstaking actions in the future or [2] go the Sweet Meteor of Death route and nuke their website from orbit.

It ain’t pretty, fam. Buckle up!