Pushing Content to Production Best Practices

Ensure that you have the Account Manager role to push content to Production. You can also maintain an updated list of authorized users for content deployment. For more information, see Whatfix User Roles.

Before initiating a push to Production, thoroughly review and ensure that all Advanced Customization and Style settings are configured as desired. Confirm that all configurations are set to be pushed to production along with the content and/or widgets.

Verify that all publishing content is in the Ready stage before initiating the push. When pushing linked content, ensure both the content and associated widgets are in the Ready stage to avoid any inconsistencies.

Prioritize content testing and ensure that any potential issues are addressed before pushing the content.

Before confirming the push to Production, review the Summary pop-up to verify that only the intended content is being pushed. Confirm that the content matches the planned deployment and no unintended changes are included. For more information, see Summary Pop-ups for Push to Production.

You can publish changes like global themes and configurations, User Actions, and other account-level changes, and more, without having to push any content/widgets to Production along with them.
Go to an empty Ready stage and click Publish changes. Review your changes in the popup that appears, and click Push to production. For more information, see Should I do a Push to Production for any content changes?

Plan and execute push to Production in a release management fashion rather than publishing every single update. Consolidate multiple changes into well-organized releases to streamline the deployment process.

Group content or widgets that you want to display to users belonging to the same geography, having the same user roles, and more. Push the Folder to Production to ensure all related content and/or widgets is published together. For more information, see Organize Content/Widgets using Folders.

Ensure that the correct version of the content is selected for deployment. Avoid pushing outdated or incorrect versions by double-checking the version details. For more information, see Content Versioning.

After pushing content to Production, check your email and the notification center to confirm that the content has been successfully published.