Skip to Content
Browse documentation

Create a RAPP Theme

Create matching RAPP template and static directories, preserve panel behavior and select the custom interface theme.

The RAPP interface uses Django templates with matching static assets. Use a new unique theme identifier such as mytheme; preserve the shipped default directories.

Copy both parts

On a development server, first ensure neither destination exists. Then create the template and asset copies:

test ! -e /usr/local/eenos/rapp/templates/mytheme && cp -a /usr/local/eenos/rapp/templates/default /usr/local/eenos/rapp/templates/mytheme
test ! -e /usr/local/eenos/rapp/public/static/mytheme && cp -a /usr/local/eenos/rapp/public/static/default /usr/local/eenos/rapp/public/static/mytheme

These are administrative copy examples, not commands to run against a server without a planned theme deployment. They refuse to copy onto an existing destination; check both outcomes before proceeding. Preserve ownership/readability appropriate to the panel runtime.

Customize safely

Edit /usr/local/eenos/rapp/templates/mytheme/ and add assets under /usr/local/eenos/rapp/public/static/mytheme/. Theme discovery requires both directories and a valid identifier; a templates-only copy does not appear as a complete theme.

Preserve template inheritance, form methods/actions, CSRF tokens, translated strings, route names, data attributes and required JavaScript. Keep asset references theme-aware rather than hardcoding default throughout your copy. Maintain app assets too: an extension installed before the new theme existed may need its files copied into the new theme's static directory.

Select and verify

Use the account's Default Theme controls to select the installed identifier, subject to current account permissions and demo restrictions. The RAPP theme context uses the authenticated account's session preference with its configured fallback. A custom interface theme is separate from appearance-mode toggles and branding.

Test login/logout, navigation, forms and validation, language selection, AJAX tables, file tools and conditional app menus. Verify the account actually renders the intended template and static files in fresh sessions. Keep the default option available for rollback; do not remove a theme while accounts still select it.

Maintain after updates

Custom copies do not inherit upstream fixes automatically. Compare them with updated defaults and merge functional, security and accessibility changes. Test supported light/dark modes and responsive sizes before release. The generic plugin installer is not a theme update/rollback manager.