-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: applet theme - reskinning #1864
Comments
@BarrySunderland @WorldImpex how can I test this feature? |
@natalia-muzyka There should be a way to define which skin the editor wants for the applet in the builder |
As documented above:
There is an API Endpoint (CRUD) which can be use by the developer or admin to set themes in the database.
If no themes are defined, set in the database, there are no themes available in the administration panel respectively the editor cannot select a theme. If there are themes defined, then a dropdown with a list of themes is made available in the applet builder of the administration console. |
@peterpeterparker When will a theme be added so we can QA? |
Do not know. That should probably be discussed between Wil, Anirudh and @BarrySunderland For QA I guess you can also define "a theme", does not have to be "the theme". |
Applet themes are applied according to the selected in the applet builder themes: Theme 2 Few things that I mentioned:
Question: Environment: |
@natalia-muzyka Yes these are expected behaviors. Thanks for the detailed write up! |
As per the comment above, the requirements are met. Verified and closed. |
Feature Description
For the cooperation with external studies, it was suggested that applets' design should becomes more flexible to adapt external studies. To limit the scope of the feature, the idea is to introduce themes, so that a theme (a set of predefined style) can be applied to an applet.
Themes have to be configured by the team in the database, there is no GUI to create and handle these.
If no themes are defined, no theme should appear in the administration panel and nothing should change across the platform and apps, UI remains the same.
To the contrary, if themes are defined in the database, upon creating or editing an applet in the admin, user should be able to select a theme. To do so, a dropdown of themes will be presented on the applet' details page.
If a theme is selected and therefore save with the applet data, the UI of the applet should inherits the theming, its options, in the mobile application.
Scope of the theming is limited to following option:
All theming options are optional and once again, have to be defined by the team.
Screenshots
Logo:
Header and footer with primary color + custom backgroung:
The text was updated successfully, but these errors were encountered: