Modifying the dynamic resource references for your theme | HCL Digital Experience

Modify the dynamic resource references so that you can link to the static resources for your theme.

About this task

Dynamic content spots are defined through a module called wp_dynamicContentSpots_85. The module is defined in the plugin.xml file, which was copied when you copied your theme.

Procedure

Open the plugin.xml from the CustomThemeDynamic project that you created when you copied your dynamic theme resources.

Edit the IDs and names to have unique custom names. Use custom plug-in IDs with the prefix of your company name to ensure that your WAR files are invalidated. The following code block shows an example.

<?xml version="1.0" encoding="UTF-8"?>
<plugin id="com.yourcompany.customtheme" name="Custom Theme Modules provider-name="Your Company" version="1.0.0">

<extension id="wp_dynamicContentSpots_custom" point="com.ibm.portal.resourceaggregator.module">
   <module id="wp_dynamicContentSpots_custom">
      <contribution type="dyn-cs">
         <sub-contribution type="markup" ref-id="customtheme_footer">
            <uri value="res:{war:contextroot}/themes/html/dynamicSpots/footer.jsp"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_crumbTrail">
            <uri value="mvc:res:{war:contextroot}/themes/html/dynamicSpots/crumbTrail.jsp,smartphone@"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_topNav">
            <uri value="mvc:smartphone/tablet@res:{war:contextroot}/themes/html/dynamicSpots/navigation.jsp?type=top"/>"
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_primaryNav">
            <uri value="mvc:res:{war:contextroot}/themes/html/dynamicSpots/navigation.jsp?type=primary,smartphone@,tablet@"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_secondaryNav">
            <uri value="mvc:res:{war:contextroot}/themes/html/dynamicSpots/navigation.jsp?type=secondary,smartphone@,tablet@"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_sideNav">
            <uri value="mvc:res:{war:contextroot}/themes/html/dynamicSpots/sideNavigation.jsp?startLevel=2,smartphone@,tablet@"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_mobileNav">
            <uri value="mvc:smartphone/tablet@res:{war:contextroot}/themes/html/dynamicSpots/mobileNavigation.jsp"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_commonActions">
            <uri value="res:{war:contextroot}/themes/html/dynamicSpots/commonActions.jsp"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_layout">
            <uri value="lm:template"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="85theme_toolbar">
            <uri value="mc:wp_toolbar85@mvc:dyn-cs%3Aid%3A85toolbar%2Csmartphone%40%2Ctablet%40"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_head">
            <uri value="res:{war:contextroot}/themes/html/dynamicSpots/head.jsp"/>
         </sub-contribution>
         <sub-contribution type="markup" ref-id="customtheme_status">
            <uri value="mc:wp_status_bar@res:{war:contextroot}/themes/html/dynamicSpots/status.jsp"/>
         </sub-contribution>
      </contribution>
   </module>
</extension>

Access the CustomThemeStatic project that you created when you copied your static theme and skin resources.
Modify the profiles for your custom theme to include the module in your plugin.xml.
1. From the WebContent/themes/customTheme/profiles folder, edit each profile file.
2. Replace the wp_dynamicContentSpots_85 module with the wp_dynamicContentSpots_custom module that you created when you modified the plugin.xml.
3. Save your changes.
From the WebContent/themes/customTheme/profiles/nls folder, edit the theme_en.html file (or whichever file is your default locale) on your local drive. Repeat for any of the other locale files for languages that you support.
In the theme_lang.html files, find and replace all occurrences of 85theme with customtheme. For example, dyn-cs:id:85theme_head becomes dyn-cs: id:customtheme_head.
Save your changes.