For certain clients, use different accent colors than purple.
From Core-Styles come 9 shades and tints of the standard Portal accent color.
**Source: [`/src/lib/_imports/settings/color.accent--purple.css`](https://github.com/TACC/Core-Styles/blob/v2.26.0/src/lib/_imports/settings/color.accent--purple.css#L13-L23)**
```css
--global-color-accent--xxx-light: #f1ebfd;
--global-color-accent--xx-light: #e3d7fd;
--global-color-accent--x-light: #d5bfff;
--global-color-accent--light: #a387ed;
--global-color-accent--normal: #784fe8;
--global-color-accent--dark: #6039cc;
--global-color-accent--x-dark: #3d189b;
--global-color-accent--xx-dark: #281066;
--global-color-accent--xxx-dark: #1e0c4c;
```
Why?
Because using accent colors familiar to user will (like the logo) help retain the feeling of still being in the client domain after being redirected to an external authentication website.
Idea
For a certain client, apply new color variables by loading relevant stylesheet (see example content below) from relevant repository (to ensure that client manages colors) at relevant version (so colors will not change unexpectedly).
Pseudo-Code
In a base template e.g. [`/service/templates/base-auth.html`](https://github.com/tapis-project/authenticator/blob/v1.5.0/service/templates/base-auth.html):
- if client = designsafe
- then render ``
E.g. [``](https://github.com/TACC/Core-Styles/blob/0ee8727/dist/settings/color--tapis-project-authenticator-67-example.css)
The request originated from TACC's CMD team when it saw new DesignSafe using TAPIs Login. I intend to provide DesignSafe accent colors stylesheet for this. Unscheduled task.
Request
For certain clients, use different accent colors than purple.
From Core-Styles come 9 shades and tints of the standard Portal accent color.
**Source: [`/src/lib/_imports/settings/color.accent--purple.css`](https://github.com/TACC/Core-Styles/blob/v2.26.0/src/lib/_imports/settings/color.accent--purple.css#L13-L23)** ```css --global-color-accent--xxx-light: #f1ebfd; --global-color-accent--xx-light: #e3d7fd; --global-color-accent--x-light: #d5bfff; --global-color-accent--light: #a387ed; --global-color-accent--normal: #784fe8; --global-color-accent--dark: #6039cc; --global-color-accent--x-dark: #3d189b; --global-color-accent--xx-dark: #281066; --global-color-accent--xxx-dark: #1e0c4c; ```Why?
Because using accent colors familiar to user will (like the logo) help retain the feeling of still being in the client domain after being redirected to an external authentication website.
Idea
For a certain client, apply new color variables by loading relevant stylesheet (see example content below) from relevant repository (to ensure that client manages colors) at relevant version (so colors will not change unexpectedly).
Pseudo-Code
In a base template e.g. [`/service/templates/base-auth.html`](https://github.com/tapis-project/authenticator/blob/v1.5.0/service/templates/base-auth.html): - if client = designsafe - then render `` E.g. [``](https://github.com/TACC/Core-Styles/blob/0ee8727/dist/settings/color--tapis-project-authenticator-67-example.css)