Automate your infrastructure to build, deploy, manage, and secure applications in modern cloud, hybrid, and on-premises environments.
The dot-com boom followed and websites became a must for every business that wants to grow. The emergence of traditional content management systems (CMS) helped companies build and maintain a strong and meaningful web presence. But in recent years, things have started to change.
The increasing use of mobile devices and apps, as well as IoT (the internet of things—smart watches, kiosks, billboards, smart home devices, etc.) introduced completely new challenges and avenues for the business owners to explore. Just having a website is hardly enough anymore.
Companies now have to build applications that are consistent with their websites' look, feel and content. This has doubled the work, increased the time to market and the overall cost of ownership. The traditional CMS platforms have started to fall short.
That’s when a new trend started taking shape, the so-called headless CMS. Headless content management systems, unlike the traditional type, are not bound to a specific delivery channel such as a website. There is actually no delivery channel available out-of-the-box (no head, hence the name). The content is made available for consumption through APIs, which can be used for building websites, mobile apps, IoT device integrations or even integrations with different third-party systems.
A headless CMS comes with many advantages:
But there are some disadvantages to a Headless CMS as well:
As we can see, using a headless CMS is not a silver bullet, after all. Although companies get a lot of flexibility and a wealth of new capabilities, which traditional content management systems fail to offer, there always are new challenges to face and new requirements to deal with. If only there was anything that could provide the level of flexibility of headless without sacrificing the benefits of a traditional CMS...
Mix a traditional and a headless CMS, with a pinch of tech-stack evolution, and you get a decoupled CMS. The decoupled CMS is different from the traditional CMS in the sense that content management is independent of the presentation layer.
A prerequisite for achieving this is for the CMS to have an underlying architecture that enables managing and storing content separately from the pages and templates that will be used for displaying the content. Another aspect of the decoupled CMS is that the content management is exposed via APIs for use by different consumers just like it is with the headless CMS.
Having the same APIs in place, a decoupled CMS inherits all the benefits of a headless platform: frontend agnostic content, fast and cost-efficient multi-channel delivery, future proof and easy to integrate with third-party systems.
But by keeping the publishing tools of the traditional CMS, a decoupled CMS eliminates many of the disadvantages of headless. The initial cost of starting a project is reduced since the CMS comes with all the tooling to create the main publishing channel. Marketers can easily create personalized landing pages using the WYSIWYG editors without relying on developers.
To answer this question, we are going to delve deep into what Sitefinity is made of. Let’s start with architecture. Since the major overhaul with v4.0 back in 2010, the content management has been completely separated from the page and template editing. The pages consist of layouts and widgets created by designers and developers, which consume the content created by editors. Decoupled architecture? Check.
What about APIs? On top of its easily extendable native APIs, Sitefinity provides full-blown OData REST APIs for all existing and dynamically created content types in the system. OData is a powerful open source and open protocol technology that defines a set of best practices for building and consuming RESTful APIs.
Client applications such as SPAs, mobile apps, IoT apps can easily consume content by using a standard-compliant REST API calls or by taking advantage of the Sitefinity WebServices SDK.
With recent versions of Sitefinity, OData services can also be used to retrieve metadata for the website page structure and use this metadata to build applications that mimic the pages, layout and content available on the website. This approach is the foundation of the new out-of-the box frontend layer of Sitefinity that is being built on .Net Core.
Here’s a great post if you want to learn more about the Sitefinity 3-tier architecture and .NET Core.
With a decoupled architecture at its core, with powerful, easy to consume APIs and with a rich toolset for the presentation layer, Sitefinity is a genuinely decoupled CMS that fosters omnichannel delivery and lets you unlock the development potential by leveraging more and better frontend technologies as they emerge and evolve.
Start a Free Trial of Sitefinity
Ferdi Nebiev is an engineering manager at Progress, leading one of the Sitefinity core teams. He has been working on Sitefinity for seven years, enjoying a journey that started all the way back at version 6. Ferdi's extensive background as a developer and scrum master and his commitment to continuous learning and product development have been key assets in his No. 1 objective of helping customers get the most out of a platform we all use daily to deliver value and connect with our communities.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
You have the right to request deletion of your Personal Information at any time.
You can also ask us not to pass your Personal Information to third parties here: Do Not Sell My Info
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.