- Last Modified:
- 06 Jun 2019
- User Level:
- Power User
If the updates require changes to Page Layouts, Content Types or Navigation Objects, consider reading our our Guide to Developing and Testing in TERMINALFOUR.
Instead of updating the main CSS file, which may contain Media T4 Tags within the Media Library, it can be useful to keep the updates within separate files. Since CSS ordering dictates precedence you can update a separate stylesheet that is linked to last. When the development is ready to implement into TERMINALFOUR, the changes can then be put into the main file.
Update in TERMINALFOUR
Once the changes have been tested locally, and are ready to be updated in TERMINALFOUR, there are a few approaches, depending on the volume and complexity of updates.
Low Risk and Minor Updates
For very minor updates, that only impact single Page Layouts or Content Types, it can be possible to update the files in the Media Library, preview the relevant pages to test, and then publish. This should only be done for updates that are small and low risk, that would not have a big impact on the site.
Medium Risk Updates
High Risk and Extensive Updates
For large updates, that are site-wide or high impact, it may be worth implementing the updated files in a test or development environment of TERMINALFOUR. This will allow you to publish out the full test site with the updated CSS/JS, for site-wide testing. Once tests have been completed and are successful, the changes can then be implemented in the Production environment. In this case, you may choose to temporarily suspend the scheduled publish and/or transfer of the site to allow the updates to be completed and checked before the site is published and/or transferred to live.Back to top