If you are happy with the template structure, and only want to update the HTML and CSS for the templates, this is probably the best option.
This mode can be turned on through the user interface and, once on, we are effectively in a state of "template freeze" for the duration of the template work. This may last 2 days or 2 weeks, depending on the changes required and number of templates that need changing.
Once in site migration mode, a separate publishing server needs to be set up in order to view the changes to the templates.
The major benefit to this process is that it allows your editorial team to carry out work as usual. Normal page content such as news, events, images, and documentation can still be published for the duration of the redesign process.
When you are ready to go-live with the new designs, simply switch IIS to point to your new site migration server or exit site migration mode and begin a live site republish.
If you need to restructure the templates or change templates for entire sections, then template switching is the way forward.
The first step is to design a new set of templates including new CSS, HTML, web controls, and other logic. Secondly, we recommend you use Contensis to fully test your pages on your built-in preview server.
Then finally use the template switching tool to select a project, a folder, and then your intended templates.
You can check whether the placeholder content can be mapped directly or if you need to cater for subsidiary content in any way. You can then start the switch and move content over to the new designs within a few minutes.
Allow users permissions to edit any template-based asset and preview it within the context of your preview website. Before moving to live page URLs, the changes can be checked and approved.
Any changes can be rolled back using full version control.