So you are all set with the content updates for the web page. Great! But are you sure on how the content will be appearing live? That’s where the staging module will come into the picture. Staging module allows you to easily transfer changes made to pages or objects in a Kentico instance on one server to a different instance on another server. You can also perform complete synchronization of all pages and objects. All connected instances must use the same version of Kentico. Staging is particularly useful if you need to synchronize multiple environments during development, for example:
Development > Testing/Staging > Live (production)
WHAT IS CONTENT STAGING
Content staging is the practice of deploying changes to one or more servers outside of the development environment, such as content review, quality assurance, security validation or performance testing, before deploying to production. Despite the name, content staging is not just about staging visible content.
Why stage content? Organizations have many reasons for wanting to stage changes prior to deploying to production:
- Does the content adhere to organizational compliance policies and standards?
- Is the content grammatically correct?
- Have accessibility requirements been taken into account?
- Has a custom component/code been tested?
- Does a new template or layout adhere to organizational or departmental design guidelines?
- Does the content duplicate existing content?
KEY ADVANTAGES OF STAGING MODULE
● Review All Content Before It Gets Published
The Staging module synchronizes content from your authoring environment to the live server. You can review all changes made to the site on your local server before showing them to the visitors.
● Separate Authoring and Live Environments
Content staging not only adds extra approval and QA steps to your publishing process, but it also separates the authoring and lives environment. It means you can disable the administration interface on the live site and make all changes on your local server to increase security.
Having an internal authoring server also improves the user experience for your content administrators as they access their internal server, instead of making changes on the live server.
● Publish Content to Geographically Distant Servers
Since you can synchronize content to multiple servers at the same time, you can run multiple geographically distant Kentico CMS servers around the world and keep their content synchronized with your authoring server. It’s useful when you need to run servers in Europe, North America, Australia, and China at the same time while providing site visitors with a highly responsive website.
● Deploy New Templates and Other Code Across Servers
As with content, you can also synchronize development objects, such as page templates, CSS stylesheets, transformations, and others, across servers. This makes incremental updates of the website possible with only a few clicks.