...
| Code Block |
|---|
<context-param> <param-name>frevvo.oem.branding.class</param-name> <param-value>oem</param-value> <description>This css class will be placed onto the body of the frevvo ui pages. OEMs can then create their own private CSS file(s) with rules based on the body having the oem branding class in oem branding class order in order to customize the frevvo app.</description> </context-param> |
CSS file(s) with rules based on the body having the oem branding class can be created in order to customize the application. If you do not wish to create css files from scratch, the default oem-branding.css file is a good place to start.. Any aspect of this file can be changed. The oem-branding-.css file is located in <\tmp>\css-XXXXX, where XXXXX=version number\themes\oem directory of the unzipped WAR.
OEM partners are responsible for creating the CSS file(s) and putting them into the WAR file. To do this, edit <\tmp>\css-XXXXX\/form.pac.css (in the exploded WAR) and add one or more lines like the following: @IMPORT url(“oem_branding.css”); where oem_branding.css is the name of the css file containing the specific oem rules. XXXXX=the version number.
...