You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Admins should be able to deploy Mattermost and specify custom themes in place of the existing ones (or an addition to the existing ones) without having to patch mattermost-webapp. This could be done in a number of ways (e.g. configuration or being stored in the database), but should persist across version upgrades.
Additionally it would be ideal if admins could specify the default theme for users, as well as having full control over the list of themes available.
Observed behavior (that appears unintentional)
Currently we patch mattermost-webapp, making changes to components/admin_console/admin_definition.jsx, utils/constants.jsx and including custom images in images/themes that we reference in the changes we've made to utils/constants.jsx.
The text was updated successfully, but these errors were encountered:
Summary
This is a feature request for an easier method for admins to include custom themes.
Steps to reproduce
Currently deploying a Mattermost instance with custom themes (for instance, company-branded colours) requires manually patching https://github.com/mattermost/mattermost-webapp.
Expected behavior
Admins should be able to deploy Mattermost and specify custom themes in place of the existing ones (or an addition to the existing ones) without having to patch mattermost-webapp. This could be done in a number of ways (e.g. configuration or being stored in the database), but should persist across version upgrades.
Additionally it would be ideal if admins could specify the default theme for users, as well as having full control over the list of themes available.
Observed behavior (that appears unintentional)
Currently we patch mattermost-webapp, making changes to
components/admin_console/admin_definition.jsx
,utils/constants.jsx
and including custom images inimages/themes
that we reference in the changes we've made toutils/constants.jsx
.The text was updated successfully, but these errors were encountered: