What is currently the recommended publishing workflow for Content Pages

Hello Everyone,

Every since in a while, I receive questions about the best Content Page authoring workflow in Liferay. It should support some form of versioning, bundle multiple changes together (so one can go live with the entire changeset, not individual updates that could make the site inconsistent for a while), and allow review before publication. Liferay has two mechanisms that try to satisfy these requirements: Staging and Publications (Publishing Tools - Liferay Official Documentation - Liferay Learn). Staging is complex and heavy, and for a long time was not recommended by Liferay, except some specific cases. As a result, the only way to get a more complex authoring workflow was to use Publications (which were really complex as well). Since 2026.Q1, though, they have been put into maintenance mode, so I understand they are not recommended either.

My question now is: should we use Staging to achieve a better Content Pages authoring workflow, or is something else planned to come out soon, like the content page history?

Staging is really heavy, so I’d like to avoid using it. It also cannot really be applied just to Content Pages, but Web Contents and Documents must also be included (otherwise they are not visible in the Staging area, so the site is not previewable).

Thank you!

KG

1 Answer

1

Hey @kgolebiowski, you can already to this if you just don’t publish the page, the changes are kept on the draft version on top of it. If you want to do this in a more controlled approach, we are solving this in Q1.27 with our new Launches Framework, you will be able to work in a separated “version” of the page where all your changes to that page will go live once you publish that launch.

Hi Luiz, we use the Draft version, but it is an extremely basic workflow that misses crucial content authoring features like versioning (with rollback), review by non-editors, and publishing multiple changes at once. The Publications were a mechanism that filled some of these gaps, but they were very complex and forced users to create and process a full publication even for simple changes, where regular versioning would be enough. Having said that, I'm really looking forward to the new Launches Framework you mentioned. Do you have a brief description of how it's going to work?

–