2012 Style to Classic Template Refresh in 2016.1

Information about the changes to the 2012 Style Templates (now named Classic) introduced in 2016.1

The 2016.1 version includes a comprehensive refresh of the underlying components of the "2012 Style" Templates; now renamed "Classic". Although functionally and visually identical to the 2012 Style Templates, the Classic Templates feature a modernized Javascript core and standardized set of CSS selectors.

These changes were made to ensure that the Templates retain broad compatibility with both Web Browser and Compiled Help outputs, whilst taking advantage of a common set of CSS selector names that will make it much simpler to manage Style Rules in custom Templates, override standard Template Style Rules and share custom Style Style Rules amongst different Templates. The improvements to the Javascript core will improve long term compatibility of the template with modern browsers and our ability to implement new features and fix browser compatibility issues.

Projects using the 2012 Style Templates will be automatically migrated to use the Classic Templates when they are opened.

If you are currently using any Custom Templates based on the 2012 Style Templates, those Templates will continue to work without modification, but we recommend you consider migrating to new Custom Templates based on the Classic Templates. You can find more information on how to migrate your Custom Templates here: Upgrading Custom Templates based on 2012 Style Templates