Liferay CMS for a retail content workflow
Assess Liferay’s content and experience tools for retail publishing, comparing editorial controls, integration work and the customer-facing result.
- Published
- Last updated
Liferay CMS can manage retail guides and policies with structured content, approval workflows and delivery to Liferay pages or an external site. It suits a retailer that needs shared publishing across teams or channels and has technical support for the delivery layer. Start by naming the Liferay product and version in the proposal: classic Web Content and the newer CMS have different workflows.
Define the Liferay retail content role
Give Liferay responsibility for approved editorial content, with a separate owner for commerce records and customer access. A buying guide can explain how to choose a product. Its displayed stock and order status need the systems that own those records.
Separate the work before comparing content management systems.
| Content | Retail example | Ownership decision |
|---|---|---|
| Public guidance | Delivery policy or appliance buying guide | Editorial team approves wording and public availability |
| Account-specific content | Instructions for a contracted trade account | Account owner approves the audience and access rules |
| Media | Product care PDF or guide images | Asset owner controls versions, rights and replacement |
| Transactional records | Inventory, payment or order status | Commerce system owns the record and permitted access |
Liferay’s CMS documentation describes content and file structures organised into spaces. That lets a team model a policy separately from its page design. Decide which fields editors must complete, such as policy text, audience and supporting document. Keep sensitive account details out of a public content type.
A digital experience platform (DXP) proposal can also cover commerce, personalisation and portals. List those as separate implementation responsibilities. A content workflow alone doesn’t establish how a customer signs in or how the site retrieves their order.
Compare the documented publishing workflow
Assess a specific Liferay deployment by following one policy from its content structure to its displayed page. Liferay documents the newer CMS as generally available in DXP 2026.Q3. Its classic Web Content application is in maintenance mode from DXP 2026.Q1. An existing classic implementation can continue alongside the newer CMS, so match the demonstration to the system you’ll operate.
For the newer CMS, content structures define fields and the spaces where a type is available. Have an editor create a delivery policy with a required body and an optional file. Have a separate approver handle publication. Document who can alter the structure itself, because changing a field affects more than one article.
Check permissions with actual roles. Editing rights, approval rights and customer viewing rights answer different questions. For a multisite retailer, identify the spaces shared by brands and the sites that consume each policy. Specify where local wording is allowed and who corrects a shared mistake.
Liferay’s content preview lets editors select a connected site and display page template, or an external URL. Include the chosen preview arrangement in the implementation. A content form preview cannot establish how an independently built storefront renders every field.
For an external site, the CMS delivery guide uses object APIs with OAuth 2 authorisation. Its REST /approved endpoints read published content. GraphQL returns the latest entry version in any status, so a public feed needs a deliberate publication filter. Keep application secrets on the server. For account content, use the reader’s permissions or enforce account access in your application before returning content.
Liferay’s subscription options distinguish software as a service, platform as a service and self-hosted deployments. Compare the written subscription and licence terms for the proposed product with implementation and ongoing operation. Include frontend development, identity integration, hosting and maintenance in the estimate. Open-source availability doesn’t establish the terms or support included in a commercial DXP proposal.
Check the customer-facing correction
Trace an approved policy correction through every consuming page and confirm that each intended customer receives the revised answer. Use a non-production copy with test accounts for the acceptance check.
For a hypothetical retailer, change an incorrect delivery window in a shared policy. Keep the original version available for a recovery exercise. Record the policy identifier and all public or account pages that use it.
- Save the correction as a draft. Confirm that customers still receive the approved version and cannot open the draft through a direct URL or API request.
- Preview the policy on its intended page. Inspect the linked PDF and the mobile layout, then send the change through its approval workflow.
- Publish and follow the delivery path. For an external site, inspect the returned content and any rebuild or cache refresh before opening the customer page in a fresh session.
- Compare a signed-out visitor with an authorised account and an unrelated account. Public wording must appear publicly, while account-specific wording stays within its assigned audience.
- Restore the previous version and repeat the delivery check. Confirm what becomes visible, then republish the correction through approval.
Liferay’s asset history instructions say a restored version becomes the latest version while retaining its workflow status. Expired or deleted versions cannot be restored. Also, DXP Publications doesn’t track newer CMS content or structure changes, so define recovery for those changes separately.
If the content API returns the correction while the page shows old wording, inspect the site’s cache or build step. If the wrong account sees restricted content, inspect delivery permissions and application authorisation before approving the arrangement. Choose the proposed Liferay workflow when your editors can complete this correction and recovery process within the responsibilities your team can maintain.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.