Handling common customizations

After the themes and skins are modularized, update any customizations you have.

Parent: Update a Page Builder theme to use Dojo 1.6

Style changes

In customizing the existing theme, it is possible that you modified some of the styles in the OneUI .css files. To preserve those changes in the new modularized theme:

1. Copy any style class definitions that you customized into their own .css files, if they are not already.

2. Place the .css files in the fs-type1 WebDAV \themes\YourTheme\css folder, and add the .css files as head module contributions to the main theme module.

3. If you have a large amount of style classes, we can create our own module and place the .css files its war location. Create a module definition for the module and add the .css head contributions to it.

4. Run the theme and ensure that the style class names are unique and do not conflict with other style class names that are loaded by other modules, such as the newer wp_one_ui_21 OneUI module. Rename any style classes that are not intended to be overrides to be unique names. If we use intended overrides, intentional reuse of the same style class name, then verify the other module with the same style class names is a prerequisite to the module with the .css contributions. The prerequisite ensures that the original style classes link on the page before the overrides link on the page, which causes the overrides to be used.

Move forward do not modify the OneUI style classes directly. OneUI is its own shared module now, so any modifications to it can be overwritten by service pack updates. Modifications would also apply to all themes that use that module, not just the one theme, which is probably not the intent. To modify the OneUI style classes make a unique copy of the OneUI module, and then modify the copy.

We can customize a small subset of the style classes without copying the entire OneUI module. Copy those certain style class definitions into a separate .css file and modify them. Then add the .css file as a head module contribution to the main theme module or other module that you created.

Navigation changes

In customizing the existing theme, it is possible that you modified or replaced the existing navigation. To preserve those changes in the new modularized theme:

1. The dynamic spot mechanism in the theme.html files still applies to modularized themes, so the navigation .jsp still works automatically through the dynamic spot in the theme.html files.

2. If the navigation is complex and uses its own resources such as .js or.css files, then consider making it a new module. The resources can then be logically grouped in one place and optimally combined when loaded.

Footer changes

In customizing the existing theme, it is possible that you modified or replaced the existing footer. To preserve those changes in the new modularized theme:

1. The dynamic spot mechanism in the theme.html files still applies to modularized themes, so the footer .jsp still works automatically through the dynamic spot in the theme.html files.

2. If the footer is complex and uses its own resources such as .js or .css files, then consider making it a new module. The resources can then be logically grouped in one place and optimally combined when loaded.