Home/Field Guide/Sites, CMS & commerce
CONCEPT 20
Publications, staging, and content delivery
Distinguish editorial approval, coordinated change sets, and environment promotion.
Pick the publication mechanism
Workflow governs approval for an item. Publications groups supported changes for review and promotion into production within the instance. Staging maintains a separate staged context and publishes supported assets to a local or remote live environment. Review documented compatibility before enabling publishing tools together. A CI/CD release deploys code and configuration separately.
Work a campaign release
For a new partner launch, first define and approve the content. Create a change set for supported page changes, review its dependency and conflict reports, and coordinate the activation date with the content team. Test the public URL and relevant roles immediately after publishing.
Check coverage for every changed asset type. In current Liferay CMS documentation, Publications does not track the new CMS’s site content or structure changes. Schedule those changes through the CMS’s supported lifecycle. For a page linking to an attachment, test both assets and their role grants across the boundary.
Plan recovery
Capture the affected URLs, owners, permissions, and timing. Identify which change types can be reverted by tooling and which need a new edit or restored artifact. An application rollback alone cannot reverse externally delivered notifications or delete an integration’s downstream state. Verify the recovery procedure with a failed release simulation.