The extension mechanism of eXo Platform enables the skin definition to be replaced with the skin resource configured in your extension. This is the example where the CSS path of default portal skin needs to be modified without touching the eXo Platform's files.
<gatein-resources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_resources_1_3 http://www.gatein.org/xml/ns/gatein_resources_1_3"
xmlns="http://www.gatein.org/xml/ns/gatein_resources_1_3">
<portal-skin>
<skin-name>Default</skin-name>
<skin-module>myintranet-css</skin-module>
<css-path>/templates/skin/DefaultStylesheet.css</css-path>
</portal-skin>
</gatein-resources>
Accordingly, the CSS will always be inserted into all pages of a given site. The <css-path> tag specifies the path for skin's stylesheet in your custom-extension.war.
The common usecases when you customize a site skin include: