With almost 2 billion websites in existence and 100+ CMS vendors enabling these websites, it’s important to clarify that the intent of this post is to focus on enterprise-class CMS needs. That is how to deliver content and display content for mid-to-large companies that meet one or more of the following criteria either today or in the near future that require:
The common representation of an enterprise-class CMS typically includes reference to a backend and a frontend. When it comes to traditional content management systems, or “coupled” CMS, these two functions are part of the same vendor platform, intrinsically linked through custom code.
As previously described, the first CMSs were developed to support one type of channel: websites. As a result, many of the industry’s first vendor-driven CMSs were designed as monolithic applications in which the user interface and data access code are combined into a single program to form a single platform.
More specifically, monolithic CMSs have been developed with the frontend and backend being designed into a single platform. At the simplest level, the front-end of the CMS access content from a database in the back-end, to be used within the layout (e.g., HTML and CSS) of one channel - the website. All content is pushed to the website in a predefined manner from a layout and presentation perspective.
The greatest disadvantage of a monolithic CMS (especially when compared to headless content management systems) is its lack of modularity, resulting in difficulty for reuse of application code and regular maintenance without disrupting application usage, and most importantly, significant challenges in supporting new business opportunities such as new channels and front-end applications (e.g., single-page applications or progressive web applications).
For example, as the number of web interfaces expanded beyond the personal computer (e.g., mobile applications, web-based applications), in addition to other types of channels, the monolithic CMS rapidly became cumbersome and detrimental to business growth. Owners of monolithic CMSs were forced to spend significant resources and valuable time to support these new channels demanded by their customers. Each new channel required new content delivery and presentation templates to be created by developers and designers as well as other related front-end coding work. (refer to the below figure)
Two other disadvantages of traditional, monolithic CMSs, in addition to their inability to accommodate new channels and business models, included:
To overcome these challenges and enable companies to be more responsive to market demands, the current, the next generation CMS has evolved.
The evolution of the “old-school” CMS has been driven by continuous innovation in the software industry, a hypercompetitive market of CMS vendors and the markets’ need for competitive differentiation from a digital experience perspective. (e.g., the need to support more channels and simplify digital ecosystem complexity)
The most innovative CMS vendors today either have or are working on development of next generation CMS capabilities to help their customers: optimize content for growth and revenue, go to market in a more rapid and efficient manner, and understand the “why” of what they’re doing (i.e., practitioner insights). The following are just of few of these capabilities that serve as differentiating points as you select your next CMS vendor:
A headless CMS provides all of the capabilities of the backend of a traditional CMS (i.e., the “body”), while giving the responsibility for content presentation/layout to the delivery channels (i.e., the head). For clarification purposes, “traditional CMS” from this point forward will refer to the next generation CMS described in the prior section, with back-end and front-end as part of the same platform and vendor.
Content is no longer pushed out to a channel in a predefined manner. Content is pulled or requested from the CMS by any channel, by way of a RESTful API, enabling each individual channel to take advantage of its own unique presentation capabilities. A RESTful API is an application programming interface (API) that uses the internet protocol HTTP to request data for a data source - the CMS in this situation.
In a pure-play headless situation, the headless CMS doesn’t generate any front-end code and provides content as a service, which is why headless CMS is sometimes referred to as “Content-as-a-Service” (CaaS). This process results in the best available digital experience for the end-users of a particular device since front-end developers are able to continue developing new functionality for any channel independent of the core/backend CMS.
As Wikipedia indicates, “a headless content management system, or headless CMS, is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via a RESTful API for display on any device.” Headless CMS can also be defined as only having the ability for creating, reading, updating, and delete (CRUD) content, while downstream channels that pull content from the headless CMS are responsible for its presentation to end-users.
Why are headless CMS solutions of such high interest to so many people in today’s market? At a high level, a headless CMS is the best way to future-proof your digital experience architecture, enabling support of any channels available today or in the future. (i.e., omnichannel content management).
Just as important, developers, experienced managers, and e-commerce managers will be able to create more interactive experiences for customers in a shorter time and with less investment, reducing time to market and giving you a competitive edge. More in-depth reasons why a headless CMS platforms are of such significant value include:
Headless CMS solutions can be used to enable a content hub that can inject content into an existing CMS as well as other channels. Companies can also use a headless CMS in parallel with their existing CMS to trial and/or replace traditional CMS systems.
SMBs typically do not engage with lengthy enterprise buying processes and it is not economically viable for vendors. Buying processes are often led by end-users and developers who simply want to test how a solution works and get it up and running fast. It’s also an approach that is beginning to eat its way into how larger enterprises buy solutions, too. The way customers buy software has fundamentally changed over the past decade. WebriQ eliminates frictions in the buying and the implementation process all the way.
WebriQ has solved the two major obstacles to Headless CMS implementations;
Headless implementations are typically handling multiple vendor relationships and pricing conversations which make makes the overall Total Cost of Ownership difficult to determine quickly and accurately. With full products, W-Studio and C-Studio, WebriQ overcomes this obstacle in a big way.
Using Page Management, you can empower editors to create and manage pages for your digital solutions using reusable building blocks.
With headless CMS page management, content editors can manage your site's page tree, and page-level SEO properties, and determine what content and functionality will be on each page. Content delivery becomes a breeze.
Compared to traditional CMS, a developer and architect will still have full control over what page templates are available to the editor, where they can place modules within the page, and what the modules can do. To sum up, the benefits of Page Management:
WebriQ has a full product offering for building Microsites and Landing Pages on a Headless Infrastructure. It is a low-cost and low-risk entry to a Headless strategy for your enterprise or organization.
MACH is a set of architectural technology principles coined by commercetools that stands for Microservices, API-first, Cloud-native SaaS and Headless.
This acronym achieved widespread appeal within the commerce vendor market (here’s a short summary on what MACH architecture is for those that are not familiar).
The important thing to note with MACH is the close association with the @MACH Alliance and the relatively high barrier to entry for vendors and customers alike. The requirements to join the MACH Alliance today firmly set MACH into the Enterprise end of the market.
The MACH Alliance homepage itself highlights this Enterprise focus as a counter to legacy solutions: “Enterprise suites are no longer the safer choice. The MACH ecosystem is,”
The requirements to be a part of the MACH alliance,as well as the policing and enforcement of these requirements, helps to eliminate potential confusion in the marketplace. It actually means something to become a MACH-certified member. The MACH Alliance is like the Apple App Store: a walled garden that ensures high-quality members meet the requirements, helping to establish trust with retailers and brands.
The content schema is prebuilt and serves as the core of the publishing tool and as the only UI that users need to learn and understand.
For each page you build, you can choose from 20 different components and each component has 5 different variables.
Examples of pre-configured components are Navigation, Header, Footer, Text, Call to action, Testimonial, Portfolio, FAQs, Blog, and more.
Each page with a distinct URL can be populated with one or multiple components. All components can be reused on other pages and all components that are uniquely tagged are updated throughout all pages when content updates are done to that component. All components can be uniquely designed and branded through a Windtail CSS library.
All pages can be previewed before publishing.
SEO settings can be done on all pages separately and there is an SEO preview functionality embedded.
Last but not least, we provide the possibility to publish your WebriQ Studio to any TLD or subdomain of choice and all WebriQ Studios are de facto integrated with WebriQ analytics.
WebriQ adopts value-based pricing throughout its entire service portfolio, including WebriQ Studio.
Each customer will receive an unlimited service, for an all-in fixed monthly recurring fee. We use a unit-based approach to make creating unique and customized service packages as easy as possible. Each unit is valued at $1,000. Units can be broken into ½ units, ¼ units, or ⅛ units.
We come to value-based pricing by analyzing and quantifying any or all of the following criteria
WebriQ Studio can be expanded to a full-blown structured content data model to satisfy all digital experiences needed by your customers
A couple of examples to illustrate live implementations of large content models
Over 400 different products with multiple variations for each product, indoor and outdoor versions, and much more. All data is stored in a data lake, accessible through APIs to multiple web assets and storefronts.
All data is stored in a data lake, accessible through APIs to multiple web assets and storefronts.