On the BRYTER platform you can ensure brand compliance for various BRYTER components shown to end users, including portals, applications, modules, and data views.
Brand compliance is achieved through the use of themes. A theme defines preferred colors, logos, fonts, typography, headers, footers, and other graphical elements. When a theme is selected, it ensures that the design of the BRYTER components follows the required pattern. Themes can only be created by admins.
To work efficiently with themes, we recommend the following procedure:
- Your BRYTER admin creates the theme(s) needed for your organization using the theme editor.
- Your BRYTER admin selects one theme for an entire environment. Typically, you choose a theme that aligns with your organization’s brand requirements for both the Test and the Live environments. Consequently, if you work with different client environments, you can select a client-specific theme for each specific environment.
- Once a theme is selected for an environment, it is universally applied, determining the design of the portal, all applications, and of all modules and data views in that environment.
In most cases, authors will rely on the theme selected for the environment by the admin. However, authors also have the option to select a different theme for a module when publishing. In such cases, the module will be displayed to end users in the theme selected by the author, rather than the environment theme set by the admin. Note this is only possible for modules; applications and data views always are displayed in the environment theme.
đź’ˇ If the admin has not selected a theme for an environment, a black default BRYTER theme will be applied.