Theming

Custom Themes#

LAUTI comes bundled with an integrated theme called lauti. lauti is not shown in the backstage CMS and not directly usable but serves as a parent and blueprint for the automatically created default theme. The default theme can be modified or replaced by another custom theme. The theme loaded on startup is defined by LAUTI_THEME and LAUTI_THEMES_PATH environment variables. LAUTI_THEMES_PATH is the path to the directory where themes are stored. LAUTI_THEME can be unused and triggers the creation of the default theme or takes the name of a custom theme placed in the LAUTI_THEMES_PATH directory on the filesystem. Once a theme is activated in the backstage, this theme takes precedence over the theme defined in LAUTI_THEME.

Example:

LAUTI_THEME=mytheme
LAUTI_THEMES_PATH=themes/

Theme inheritance#

Custom themes can inherit from any other theme by specifying the parent key in theme.yaml. LAUTI prioritizes the files stored in the child theme over the files with the same name in the parent theme. Inheritance is supported for assets, templates and translations, but not for content. Custom themes need to contain all content files on their own. Custom themes created via CMS already contain all necessary content files as a copy of bundled theme lauti.