Home/Field Guide/Sites, CMS & commerce
CONCEPT 19
Classic CMS, headless CMS, and DAM
Choose a content architecture and plan governance for structures, files, and translations.
Two content models
Classic CMS uses site or asset library context and established features such as web content structures, templates, and Documents and Media. The newer Liferay CMS uses Spaces and an Object-based structure model for structured content and files. It supports content delivery into Liferay pages and other channels using APIs. Liferay identifies Classic CMS as in maintenance mode as of DXP 2026.Q1 and marks the new CMS generally available from 2026.Q3 after earlier gated releases.
| Question | Classic CMS | New Liferay CMS |
|---|---|---|
| Where does editorial ownership live? | Sites or asset libraries | Spaces and their membership |
| How is structure defined? | Web content structures and templates | Content and file structures |
| How is content delivered? | Native display tools and supported APIs | Reusable content for native pages and headless channels |
| How are changes published? | Workflow and supported publishing-tool coverage | CMS workflow and publishing behavior, separate from Publications change tracking |
Model before migrating
For a partner policy article, define a stable title, summary, effective date, locale, and attachment references. Establish taxonomy for findability and write down who approves edits and translations. Keep a mapping from existing IDs and URLs to the new model. Verify binary access, metadata, alt text, translation fallback, and redirects using a representative sample.
Prove content and file permissions
An editor may have access to a Space while a visitor only has access to delivered content. Test the same article in its page, API, and download paths. Decide whether published content or related files require a specific audience. An asset’s appearance in a listing is insufficient to prove the download endpoint enforces the intended permission.