![]() It showed itself in mobile phones, on our smart televisions, in our cars, in our virtual assistants and wearable devices. Content in its many shapes and forms started to appear all around us. Gradually our computers got smaller and less obvious. We read blogs, watched YouTube videos, and listened to podcasts on our personal computers. Content is everywhere and manifests itself in so many forms through text, audio, video, and more.įor a long time, computers and browsers were the main tool for content consumption. Why Do You Need a Headless CMS?įor starters, there’s no downplaying the role of content in today's world. “Content Management” sounds kinda boring, right? And CMS? “ESo let’s talk about how and why a CMS might help you out. And it wasn't until I started working with Strapi that I recognized my assumption. Well, we use these things to build our front ends, but we often overlook the content management side of things when we think about building a front end like that. I thought I understood Headless CMSs because to me they were “data, API, frontend” and that’s how I thought about it. Working for a CMS was like diving head first into this ecosystem. So I really like GraphQL, and that’s how I got started with Strapi. With headless you have the opportunity to tailor different experiences for different platforms all from a single content source. This is becoming a really important benefit for headless CMSs for many organizations. ![]() You need to create custom and personalized experiences Should you need to upgrade to a more modern front end or add a new front end altogether, headless makes this much easier. Going headless also means that you’re less dependent on a single solution for a front end. This is something some traditional CMSs still struggle with today. You need a secure content solutionĭecoupling the front end from the back end makes targeted attacks much harder. And for many developers, this is a critical advantage. You don’t want to give up developer flexibilityĪdopting a Headless architecture by default means that you have the flexibility of selecting a front end tool of your choosing. Monolithic vs decoupled vs headless architecturesīesides serving content to multiple platforms, there are a couple other reasons why you would want to use a Headless CMS. I like to use this diagram to illustrate how Headless works, so hopefully it paints a clearer picture. The content and its data are only accessible via calls made to the API, whether it's REST or GraphQL. What is a Headless CMS?Ī headless CMS has a back end where content is prepared – and that's it. ![]() Instead, if you want to learn more you can have a look at an article I wrote that goes deeper into various types of CMSs. In this article, however, I won’t get into the nitty-gritty of it. What is a CMS?Ī Content Management System (CMS) is a tool that helps users create, manage, and modify digital content. Since then, I have developed a pretty good understanding of what these things do – so let's get into it. And after years of ignoring CMSs as a technology, in mid 2020 I got a job at Strapi, a headless CMS tool. Life has a funny way of making you try things. I'll also introduce you to a new type of CMS that seems to be everywhere at the moment – the Headless CMS. In this article, we'll cover what CMSs are and why you should care about them. WordPress, for example, powers nearly 40% of the internet today. CMSs are pretty hard to ignore because they're everywhere on the internet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |