![]() Another way to think of this principle is to edit once, update everywhere. With all content stored in one centralized content hub, content editors can easily apply the COPE principle: Create Once, Publish Everywhere. This makes editing way easier - change the copy or image in one place, and that change applies everywhere the content is located. Unify content into a single content hubīy making content endlessly reusable, the structured content of a headless CMS eliminates manual processes like copy and pasting. Now that we’ve defined what a headless CMS is, how it works, and the ways in which it is a better solution for your content management than traditional CMS, let’s dig deeper into the value implementing headless CMS into your organization can bring. Content models are comprised of and can reuse these content types to become tailored to the unique needs of each organization, so that content creators aren’t stuck with the overly prescriptive page templates of a traditional CMS. In the example above, all of the different elements listed are considered distinct content types (author title, image, caption, body text, etc.). ![]() A content model defines and organizes all the different content types that an organization uses. The way this structured content is pulled off on the backend is through something called a content model. ![]() All these components can still be assembled to create the same webpage, but they can also be reassembled to create various iterations of the webpage, personalized for a distinct audience, reorganized for a specific campaign, or trimmed down for a mobile experience. What you see is what you get … and nothing else.Ī structured content approach separates the various elements of that page into distinct components, such as author, title, body, image, image description, definitions, e-commerce information, product pricing, terms and conditions, and more. This creates perfectly fine webpages, however, content is stuck to that format. This is often done in a WYSIWYG editor, which stands for “what you see is what you get.” Digital content creators are usually familiar with WYSIWYGs as it gives them the ability to make content edits in the backend. Unstructured content blends together all the content and code that create that webpage. To illustrate how unstructured content is typically put to work, let’s use a webpage for an example. Structured content is a general term referring to content that is broken down into small building blocks, organized in a predictable way, and classified with metadata. As long as your content is unstructured, it cannot be easily repurposed across different platforms and channels. While a headless CMS software solution enables you to deploy content across any presentation layer, it doesn’t solve an underlying problem: it does not give your content structure. APIs are the magical connection points that allow these backend systems (e.g., headless CMS) and frontend systems (e.g., website) to communicate in the specific ways a digital team wants them to. ![]() They don’t really care how that content is stored or managed. The main job of display platforms like a website or mobile app is to present content to people. It doesn’t really care what you want to do with that content. Think about headless architecture and APIs like this: the main job of a headless CMS is to store and manage your content. This is different from Wordpress and other monolithic CMSes that tightly couple the frontend with the backend, keeping you locked into how content can (and cannot) be displayed. This makes content in a headless CMS endlessly reusable, no matter the omnichannel customer experience used today, or the channels that emerge in the future. Content housed in a headless CMS is delivered via APIs for seamless display across any site, device, or other digital touchpoint. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |