Or, at least it feels<\/em> that way. It seems like we\u2019re being pressured from all sides to adopt the \u201cnext big thing\u201d, lest we be left in the dust.<\/p>\n In my thoroughly unscientific observation, many web designers appear to be frustrated with the state of things. Today, we\u2019ll talk about why that is and how taking a step back could be the solution.<\/p>\n Nowhere is the seismic shift more visible than with WordPress. The massively popular content management system has undergone significant changes in the past few years. The Gutenberg block editor and its related features make for an entirely different experience.<\/p>\n Virtually every aspect of building websites and creating content has shifted. Depending on who you ask, these changes are either infuriating or the dawn of a new era. Regardless, there has been a great amount of pressure<\/a> for web designers to adapt.<\/p>\n Whether it\u2019s the editor itself or the introduction of block-based themes<\/a>\/Full Site Editing (FSE)<\/a>, there appears to be a good bit of sentiment that these changes are being forced upon web professionals.<\/p>\n That being said, there are alternative ways to use and build with WordPress. The Classic Editor is still supported, and the traditional methods of theme creation will continue to work. No one can fully predict the future, but it seems reasonable that they\u2019ll be around for a while.<\/p>\n So, why would anyone feel forced into using something they aren\u2019t very excited about? I think a lot of it has to do with how these new features are presented.<\/p>\n In the case of 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\u2019re required to install a plugin.<\/p>\n Intended or not, this type of action establishes a narrative for users. It says, \u201cThe new way is here, and we want you to start using it immediately.\u201d<\/p>\n Pressure doesn\u2019t just come from software makers. It even goes beyond our peers and clients (as if that weren\u2019t enough). Sometimes it can come from outside parties that have a vested interest in what happens on the web.<\/p>\n Take, for example, the various initiatives that Google has implemented over the years. Whether it\u2019s a tweak to their search algorithm, the demands of its Core Web Vitals<\/a> metrics, or the push for publishers to adopt Accelerated Mobile Pages (AMP) \u2013 the company holds a lot of sway when it comes to how we build websites.<\/p>\n It\u2019s easy to see how web designers might feel at the mercy of this and other tech-heavyweights. We naturally want our websites to perform well and be easily found in search engines. Thus, it\u2019s on us to integrate their recommendations and preferences into our work.<\/p>\n And it makes sense that we\u2019d gravitate towards the companion products and services these companies offer. If we\u2019re trying to satisfy a particular requirement, it\u2019s logical to use tools that live within that ecosystem. They give us the best chance to succeed, even if we\u2019re not thrilled at the prospect of using them.<\/p>\n Again, there\u2019s a feeling of being forced into this type of arrangement. It\u2019s especially relevant in client work, where your job is to provide the best path for achieving their goals. Sure, there are alternatives. But there is also risk in going a different route.<\/p>\n What does this all mean for web designers? For one, it can lead to frustration. Among the root causes could be the great investment we make in these tools and technologies. A lot of effort goes into learning them, only to feel as though the rug is being pulled out from underneath.<\/p>\n There can also be a bit of uncertainty<\/a>. When it comes to new features, things tend to evolve quickly. What counts as a best practice today might be very different tomorrow. The result is that designers are left wondering about the right time to make a move.<\/p>\n In addition, the disruptive nature of such changes tends to throw a monkey-wrench into the daily workflow. Whether it\u2019s a new editing experience or a different coding language, it can be a struggle to get up to speed.<\/p>\n For some, the change is all too much. I\u2019ve seen several instances of designers and developers leaving behind both tools and communities that they\u2019ve contributed to.<\/p>\n One can make the argument that there will always be some level of attrition. And while that\u2019s true, it\u2019s also a negative when longtime contributors become disillusioned to the point of walking away.<\/p>\n That\u2019s not to say everyone will come to this conclusion. However, it does speak to the issue.<\/p>\n The way we work isn\u2019t just a professional concern. For many of us, it\u2019s personal<\/em>. We get attached to not only the tools we use but also to the routines we form along the way.<\/p>\n As such, some changes can be especially challenging. Add to that the prominent way new features or standards are thrust upon us and it\u2019s no wonder there\u2019s a sense of being forced to comply.<\/p>\n Yet it\u2019s also worth taking a step back and looking at the situation holistically. Quite often, there are still options within the CMS, framework, or service provider you\u2019re working with. They may require some additional action on your part, but they\u2019re available nonetheless.<\/p>\n Unless there is a major security or functionality concern, it\u2019s usually fine to stick with your current workflow. That \u201camazing\u201d new way of doing things will still be there (or not) whenever you\u2019re ready.<\/p>\n And that\u2019s the great thing about being a web designer. No matter what changes, you have a say in how you work. That\u2019s worth remembering as the web keeps on evolving.<\/p>\n The post Why Some Web Designers Are Feeling Forced into Change<\/a> appeared first on Speckyboy Design Magazine<\/a>.<\/p>\n Source: Specky Boy<\/p>\nTrusted Apps Are Switching Gears<\/h2>\n
![\"Directional](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/01\/forced-to-change-01.jpg?resize=900%2C400&ssl=1\")
<\/p>\nOutside Pressure from Big Tech<\/h2>\n
![\"A](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/01\/forced-to-change-02.jpg?resize=900%2C400&ssl=1\")
<\/p>\nThe Impact on Web Designers<\/h2>\n
![\"A](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/01\/forced-to-change-03.jpg?resize=900%2C400&ssl=1\")
<\/p>\nTaking a Holistic View<\/h2>\n