It is possible to have one header for each language of the portal, for example one header in French (fr-FR
) and one in English (en-US
).
To do so, add as many header templates as there are UI languages as in the following examples:
header.fr-FR.vm
header.en-US.vm
If the language of the portal has no corresponding header template, it reverts to using the default one: header.vm
It is possible to define a fallback mechanism. For instance, imagine an example where the following header files are available:
-
header.en-US.vm
-
header.en-GB.vm
-
header.vm
If the UI language is en
, the template generated by header.en-US.vm
is generated.
If the UI language is en-GB
, the template generated by header.en-GB.vm
is generated.
If the UI language is fr-FR
, the default template generated by header.vm
is generated.
It is strongly recommended to always use a template named "header.vm
" when adding custom headers in order to always have a fallback solution.