cs-icon.svg

About Publish Rules

Publish Rules allow you to define exactly when and how content is published or unpublished. Each rule consists of two components:

  • Parameters: Define the branches, environments, content types, actions (publish or unpublish), and languages to which the rule applies.
  • Conditions: Specify the requirements that must be met before the action is executed, such as obtaining approval or reaching a designated workflow stage.

By combining parameters and conditions, publish rules provide organizations with fine-grained control over their content release process.

This makes it easy for organizations to establish controlled content release, helping prevent unapproved or premature publishing in multilingual and enterprise settings.

Example Use Case: Enterprise Marketing Launch

A global retail brand publishes seasonal campaign pages in multiple languages. To prevent accidental live publications and ensure legal compliance, the organization defines publishing rules with the following configuration:

  • Parameters: Apply the rule to the “main” branch, “production” environment, “campaign” content type, “publish” action, and all supported locales.
  • Conditions:
    • Approver: Regional legal team and the marketing director.
    • Stage: Content must reach the “Legal Approved” stage in the workflow before it is pushed to “Production.”

This configuration prevents campaign pages from being published until the content is approved by both the legal and marketing teams and has reached the designated workflow stage. This ensures a streamlined and compliant launch process across all regions and languages.

Rule Enforcement on Content Revisions

When content is published after meeting all required conditions, the rule is not reapplied to the same version, even if it is published to a different locale or environment. However, if the content or its assets are updated, creating a new version, the rule is enforced again.

This approach streamlines publishing across locales and environments by eliminating redundant approvals, reducing delays, and ensuring timely content distribution.

For example:

In the Enterprise Marketing Launch example, the campaign is initially published once it reaches the Legal Approved stage and receives approval from the regional legal team and the marketing director. If the same version is later published in a different locale or environment, the rule is not re-triggered, as all conditions have already been met.

However, if the campaign content or assets are updated, creating a new version, the rule is enforced again. This requires fresh approvals from legal and marketing, along with confirmation that the entry has reached the “Production” stage.

Was this article helpful?
^