This makes it extremely hard to imagine the interplay between separate components, and to see how they work together to form a page.Ĭontext is everything. You can navigate up and down in the information tree, but the main focus is always on the current component. ![]() Unfortunately, the headless CMS is purely focused on content, and its visibility is almost always constricted to a single component. The particular combination of components is what makes a page a complete digital experience. Sections live below, above, to the side and sometimes even overlap. None of the components of a webpage live in isolation. Just like the actual site, it often takes time to spin up, and it’s never interactive - you still have to edit in a form-based UI, press a button, wait, and only then see the preview, costing you time at every step along the way. That’s a good and necessary step you should insist on. This problem is exacerbated by modern static sites that take longer to build, as the time an error might be in production can span several precious minutes until the whole site rebuilds, even if you correct it immediately.ĭevelopers can spend time building and properly connecting a preview environment. This is problematic on so many levels, from risking breaking a page in production, to simply shipping something that doesn’t look good. Oftentimes, this means seeing your work requires you to publish the page, i.e. Okay, so you’ve compromised and have to work with a form-based UI. Going back to a form-based UI feels like a huge step back. We’ve become very much accustomed to drag-and-drop UIs that are fully visual and reflect the end result. ![]() The same goes for image size, text wrapping on a smaller or mobile screen, etc. Selecting a color from a dropdown on a form is a counter-intuitive experience that tells the marketer almost nothing about how the live page will look. When building a website, one has to deal with a lot of visual aspects like placement, color, and even how text is positioned. We believe that you have the control of designing your own editing experience and the tools that you need.” - Dan Barak, CEO & Co-Founder, Stackbit 1. “It’s not only about combining all the pieces of the composable stack that will give you the solutions. Your teams lack independence, increasing the time to market of each change, reducing job satisfaction and, ultimately, wasting revenue opportunity. Marketers are blocked by developers and cannot change the site, while engineers spend time and effort supporting content changes instead of innovating and creating new, engaging digital experiences. Below are the challenges you can expect to encounter, or are perhaps already experiencing (and yes, at the end of this piece we’ll also make some suggestions how to overcome them, so skip ahead if you must).Īll these problems cripple team efficiency. Companies run into trouble when they expect their headless CMS to be a good editing environment for non-technical business people, like marketers. ![]() Headless CMS platforms like Contentful, Sanity, or Contentstack are amazing tools for developers. This means that developers can work on code and components, while marketers can write and edit content in a no-code UI without being dependent on developers. Their primary benefit is allowing code changes to be made independently of content changes, and vice versa. We’re assuming that if you’re here, you already know what a headless CMS is, if not, here’s a good resource to learn more about it.Īs you probably know, headless CMS are very useful. We’ll cover some of these challenges and advice on how to avoid them. This often makes your site a liability to maintain, taxing both engineering and marketing teams - rather than a revenue generating asset. A form-based interface doesn’t reflect the live, user experience, and exposes non-technical employees to the site’s complex content architecture. But headless solutions come with their own challenges. With content decoupled from the code, it can be changed quickly and independently. Headless CMS and composable architecture solutions are designed to provide a centralized content hub that can be used to create and manage content across a variety of channels. Chief among these are the difficulty of managing content across multiple channels and the inability to work independently from dependency on developers. As marketing teams create more content to engage with customers and drive business impact, they face many challenges.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |