Enable new functions in migrated themes

When you migrate your themes, migration moves your existing themes to the new server. Migration does not upgrade themes from an earlier version to use new functions that are introduced in more recent versions of the product.

When migrating modular themes, the modular theme architecture makes it easy to enable new functions in your themes by turning on and off the modules or versions of the modules. For example, if you want to update your theme to use the current version of Dojo, replace the dojoxx.json file in the capabilities folder, where xx is the version number. Your Dojo meta-modules load the newer version of Dojo as specified in the dojoxx.json file.

HCL Portal provides an optimized, modular theme architecture from Version 7.0.0.2 onward. Non-modular Version 6.1, such as Portal, PortalWeb2, and Tab Menu - Page Builder themes were deprecated in Version 8.0 and are no longer supported in Version 8.5.

Non-modular version 7.0 (Page Builder) themes are still supported on version 8.5 but are also deprecated and will be unsupported in the next version of HCL Portal. It is either required (6.1 themes) or recommended (7.0 themes) that you upgrade to a modular theme. If you are starting a new project, you must start with a copy of the 8.5 theme. If you must migrate a previous project, the older non-modular themes can physically be migrated. But, you must then manually update your themes to the modular architecture, which allows you to enable any new features.