For those of us who work on the web, the tools we use are incredibly important. We tend to get attached to them. Some of us even go out of our style to promote a particularly good one.
Over the past 15 years, WordPress has been a tool that perhaps benefitted from this loyalty like no other. A small-minded community of diehard advocates has turned into a massive one. There’s a marketplace for themes and plugins. There are numerous consumers who volunteer their time in capacities official and unofficial. Today, the WordPress community is a force to be guessed with.
As WordPress has grown into the CMS of alternative for so many, so has the criticism of its continued growth. And with the new Gutenberg editor, things have reached a fever pitch.
This elevates a few important matters. How much load should commentators carry? And, what should we reasonably are waiting for WordPress in terms of new features? Let’s dive in and see if we can find some answers.
The Sky is Falling…Or Not
The coming rollout of Gutenberg in WordPress 5.0 has garnered a lot of opinions. Since the first steps towards its invention, there has been a mixture of excite and dread within the community.
Then, as Gutenberg was liberated as a beta plugin, the stuff actually started making the devotee. While we won’t come off every criticism, suffice it to say that some customers expressed concerns of sites interrupting due to theme or plugin incompatibilities and a buggy UI. Then there used the number of those philosophical objections to parts of, or even the very existence of the project.
There are indeed a number of legitimate concerns. But there has also been an element of what I’ll respectfully describe as horror of the unknown. It too has a region in the conversation. But so often it seems to wail over everything else without adding anything productive.
However, that panic of the unknown should fade over period. As consumers become more accustomed to a change, it stands to reason that they won’t have almost as much anxiety.
Personally, this has been my own experience with Gutenberg. The more I use it and the more bug sets that get liberated, the more comfortable I am. Not to say that there still aren’t spate of areas for betterment. But at least I’m starting to see a light at the end of the tunnel.
Still, it seems like there are plenty of feeling out there. We’re visualizing a number of 1-star reviews and some developers have even begun to develop their own forks of WordPress. Fair or not, people are attached to the old-time path of doing things.
Change is Natural
What tends to get lost amongst all the hype is that, if application hangs around long enough, it’s going to change over time. WordPress just happens to be at a point where its wide usage is calling more attention to these changes.
Operating systems, for example, are famous for annoying a subset of users with UI and aspect changes( I’m looking at you, Microsoft ). Not everyone likes to change the mode they run, even if the end result really is an improved product. There is something to be said for comfort and predictability. When that’s interrupted, customers cringe.
WordPress is reported to power over 30% of the web. So, it shapes sense that a major change such as Gutenberg would cause some unrest. That number extends a whole lot of preferences, employ the circumstances and opinions.
The trick for any software developer is that they have to balance “the worlds largest” need of maintaining a viable product with stopping existing users happy. “There wasnt” easy answers, and WordPress surely isn’t immune from having to attain these difficult decisions.
You Can’t Always Get What You Want
That leads us to Gutenberg. There was, whether we agree with it or not, a determination that the Classic Editor was becoming outdated. Eventually, it was decided that a new editor was the best course to address the issue.
Knowing that you can’t delight everyone, the preferred course of action is to create the best product you are able to. Take care to ensure that it works on as many prevailing websites as possible. Take constructive criticism severely and stir compromises where you can.
WordPress has even taken this a step further. Instead of forcing Gutenberg on everyone, they have also rendered an alternative footpath. The Classic Editor plugin keeps the familiar content editing suffer and will be supported for the foreseeable future.
While that may not be the perfect solution to some, it is a way forward for those who don’t just wanted to( or unable to) change.
Even with that compromise, there will be some customers who refuse to come along for the ride. While that’s certainly not what WordPress craves, it is part of the price you pay for implementing major change. You might say that it’s a doctrine of recognizing also that you’ll lose some customers now, with the wishes of constructing greater gains in the future.
Gutenberg is Part of a Constant Evolution
I am very much a creature of habit when it comes to how I operate. For me, change means that I have to take precious time out of my day to relearn how a tool employment. It interrupts my procedure. The whole suffer is usually not something I would willingly seek out.
But I’ve also come to the level of realizing that change is inevitable. And it often pushes things in the right direction. If it didn’t, I’d still be writing HTML by hand and using tables for layout.
What’s interesting about the Classic Editor is that, in an industry that changes so quickly, it has managed to stick around for a very long time. Sure, it’s undergone incremental progress. But the basic experience has been the same. It’s always familiar and comfortable- even though it is it occasionally is a sorenes to work with.
Still, things move forward. Web design is a field that constantly challenges us to adapt to what’s new. For better or worse, Gutenberg is just one more change. We can expect that there will be more to come.
Read more: 1stwebdesigner.com