The content that you create and save on Whatfix needs to be published to the Whatfix CDN servers before it is available to your users. You might be able to view the content using the Preview mode or the See Live option (during content creation), but for the content to be live and reflected on your end user's application, you must perform a Publish action.
Here are some best practices to keep in mind when you're publishing your content to Production.
Ensure that you have the Account Manager role to publish content to Production. You can also maintain an updated list of authorized users for content deployment. For more information, see Whatfix User Roles.
Before publishing, review and ensure that all Advanced Customization and Style settings are configured as required. Confirm that all configurations are set to be publisheded to production along with the content and/or widgets.
Verify that all publishing content is in the Ready stage. When publishing 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 publishing the content.
Before publishing, review the Summary pop-up to verify that only the intended content is being published. 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.
Publish changes, such as global themes and configurations, User Actions, and other account-level changes, and more, without having to publish any content or 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. Publish 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 publishing outdated or incorrect versions by double-checking the version details. For more information, see Content Versioning.
After publishing content to Production, check your email and the notification center to confirm that the content has been successfully published.
To ensure end users' workflow does not get impacted after publishing to production, use Auto Testing to automatically test your Flows and generate an extensive report to help fix broken Flows.
For more information, see Test Whatfix Content.