Understanding Liferay CMS

To meet the demands of multi-channel delivery, organizations need an engine that operates independently of the presentation layer. By treating content strictly as data, Liferay CMS facilitates delivery to various digital touchpoints through APIs, independent of web page structures. This separation keeps your content strategy adaptable as new requirements emerge.

To grasp the value of Liferay CMS, it helps to understand how content sharing has evolved within Liferay. Historically, Liferay has used site-integrated and library-based models to manage assets. While these models remain effective for specific enterprise needs, the Liferay CMS addresses their architectural limitations to support faster, multi-channel content delivery.

Site-Specific and Global Sharing: In the Classic CMS, content is often site-scoped, meaning it is bound to the site where it was created. While Liferay’s Global site enables sharing, it often requires complex roles and permissions to restrict access to specific audiences.
Asset Libraries: Liferay introduced Asset Libraries to address scoping and reuse across multiple sites. However, their interface was designed primarily for administrators. For non-technical users, they often lack the intuitive UI and productivity tools needed for efficient daily work (e.g., robust bulk actions).

Liferay CMS represents the next step by introducing a dedicated environment built for omnichannel distribution and a modern user experience.

Liferay CMS Capabilities

By decoupling content from the presentation layer, Liferay CMS treats assets as independent resources managed within specialized repositories called spaces. This architecture empowers you to manage content in one central location and deliver it to marketing sites, mobile applications, partner portals, and more.

Liferay CMS provides a specialized toolset designed for precision and speed:

Unified Content Modeling: Define structured data and file-based assets within a single cohesive framework.
Modern Interface: Work in an environment built specifically for content creation, not portal administration.
Automated URL Management: Generate SEO-friendly, persistent URLs that stay consistent across delivery channels.
Localization Framework: Manage a brand’s voice across languages with integrated translation tools.
Scalable Governance: Define access patterns that scale automatically as asset volume increases.
Page Framework Compatibility: Use CMS content across your sites as easily as content from Classic CMS.

These capabilities are designed to work with current and future Liferay features, such as AI Hub and specialized data tools.

Choosing the Appropriate Tool

Selecting the right tool depends on your operational requirements. As a general rule, default to Liferay CMS for multi-channel projects, since it is the primary, future-proof solution.

Feature	Liferay CMS	Classic CMS
Primary Use Case	Decoupled delivery, mobile apps, and multi-channel reach.	Integrated site pages and established portal functionalities.
User Experience	Optimized for non-technical users and marketing teams.	Designed for power users and site administrators.
Architecture	Modern, standalone, and built for rapid evolution.	Monolithic and deeply integrated with the DXP core.
Content Scope	Space-scoped (independent repository).	Site or Library-scoped (primarily bound to traditional DXP sites and display frameworks).
Advanced Tools	Workflows and modern asset management.	Supports staging and publications.
Status	Active development for new features.	Maintenance mode for existing solutions.

While Liferay CMS continues to evolve, Classic CMS remains a reliable option for mature enterprise portals that require complex environment synchronization through staging or publications.

Conclusion

The move to Liferay CMS shifts Clarity from traditional site-bound content to portable, independent assets. This architecture provides an intuitive interface while ensuring your content is ready for any app or site.

Next, you’ll learn about organizing content with spaces.