Why Some Web Designers Feel Forced to Change


In life, there are certain situations where you probably should not put pressure on your luck. For example, if you see a cobra taking a nap, do not poke it with a stick. And if you run into a busy web designer, don’t force them to change their workflow. In either case, you do not like the reaction you get.

The industry seems to be going against the grain on the latter. New tools are constantly being introduced – which is great. However, with them comes the expectation that designers will race ahead and dive head on.

Or, at least it is feels that way. We seem to be under pressure from all sides to accept the “next big thing”, for fear of being left in the dust.

In my thorough unscientific observation, many web designers seem to be frustrated with the state of things. Today, we will talk about why and how to step back.

They are translated by Trusted Applications

The seismic transition is no longer visible than with WordPress. The popular content management system has undergone significant changes in recent years. Gutenberg block editor and related features create a completely different experience.

Almost every aspect of creating websites and creating content has changed. Depending on who you ask, these changes are either raging or the beginning of a new era. Regardless, there is a lot of pressure on web designers to adapt.

Whether it’s the editor itself or the introduction of block-based / Full-Site Editing (FSE) themes, there seems to be little sentiment that these changes are being applied to web professionals.

That said, there are other ways to use and build with WordPress. The Classic Editor is still supported, and the traditional methods of creating themes will continue to work. No one can fully predict the future, but it seems reasonable that they will be around for a while.

So why would you feel compelled to use something that they are not very fun about? I think it has a lot to do with how these new features are presented.

For WordPress, Gutenberg became the default editor. It was front and center, whether you wanted it or not. And if you want to go back to the old way, you have to install a plug.

Planned or not, this type of activity sets up a story for users. He says, “The new route is here, and we want you to start using it immediately.”

Pressure Off from Big Tech

Pressure does not just come from software makers. It even goes beyond our peers and clients (as if that were not enough). Sometimes it can come from external parties who have a vested interest in what happens on the web.

Take, for example, the various initiatives that Google has implemented over the years. Whether it’s a tweak to their search algorithm, the demands of its Core Web Vitals metrics, or the pressure on publishers to adopt Accelerated Mobile Pages (AMP) – the company has a huge impact on how we build websites.

It’s easy to see how web designers might feel at this mercy and other technology heavyweights. We naturally want our websites to succeed and be easily found in search engines. So, it is up to us to integrate their suggestions and options into our work.

And it makes sense that we move towards the companion products and services that these companies offer. If we are trying to satisfy a particular need, it is logical to use tools that live within that ecosystem. They give us the best chance of success, even if we are not very happy to use them.

Again, you feel compelled to enter into this type of arrangement. It is extremely relevant to the work of the clients, where your job is to provide the best way to achieve their goals. Sure, there are other options. But there is also a danger if you go the other way.

Someone who visits a Google Web site.

The Impact on Web Designers

What does all this mean for web designers? In one case, it can lead to frustration. Among the root causes that may be the great investment we make in these tools and technologies are among the root causes. It takes a lot of effort to learn them, but feel like the blanket is being taken down below.

There can also be a bit of uncertainty. When it comes to new features, things tend to change quickly. What counts as best practice today could be very different tomorrow. The result is that designers are left wondering about the right time to move.

In addition, due to the turbulent nature of these changes a monkey usually throws a key into the daily workflow. Whether it’s a new editing experience or another coding language, it can be a struggle to keep up with speed.

For some people, the change is far too great. I have seen a number of instances where designers and developers have been leaving behind the tools and communities that they have added.

It can be argued that there will always be some level of completion. And while that’s true, it’s also negative when long – term participants become disillusioned to a point of walking away.

That is not to say that everyone will come to this conclusion. However, it speaks to the issue.

Man of frustration.

Looking Holistic

The way we work is not just a professional issue. For many of us, it is personal. We are involved not only with the tools we use but also with the routines we perform along the way.

So some changes can be very challenging. Add to that the way in which we are presented with new features or standards and it’s no surprise that we feel compelled to stick to it.

But it is also worth taking a step back and looking at the situation holistically. Often, there are still options within the CMS, framework, or service provider you are working with. You may need further action, but they are still available.

Unless there are serious security or functionality concerns, it’s usually right to stick to your current workflow. That new “great” way of doing things will still be there (or not) when you are ready.

And that’s the great thing about being a web designer. No matter what the changes, you have a say in how you work. It is worth remembering that as the network continues to develop.



Source link

By LocalBizWebsiteDesign

Leave a Reply

Your email address will not be published. Required fields are marked *