New Styleguide page for "Loading" | |
Introduce CDN links to all images | |
Add Section with index-tiles to branding page | |
New Styleguide page for "Branding" | |
FC | Extend ".wui-bs-alert" with all fruit-color-variantes |
Font-Awesome has been updated to version 5.12.0 | |
Ut | "Utils" has been extended with opacity, heights and colors |
Do you have any design-related questions or suggestions? We'd love to hear from you.
Please contact Wuiman to discuss your ideas.
If you are wondering which colors can be changed, when we use which colors and what you have to pay attention to, then you have come to the right place. On the utils page you you can also find a detailed overview of the respective classes and variables we use in wescale. On the branding page You can see what the colors will look like on the platform.
rgb 110|90|191
$color-primary
On almost every page, the primary action is triggered by a button. This allows us to guide the user through the system and support her in completing tasks as quickly and easily as possible. Accordingly, all buttons that trigger a primary or secondary action have the color $color-primary.
Due to our concept of user guidance, this color is reserved for buttons in most cases. (see: Buttons)
rgb 45|119|201
$color-active
The active color is used in every element which has a state that can change. The user recognizes at a glance which UI element is active or which element can be activated. It does not matter whether the element was activated by a user or by the system.
rgb 7|131|144
$color-highlight
In reality, there is often a thin line between highlight and active color. A good indicator for the use of $color-highlight is that the element is neither clickable nor changes its state.
These colors are only partially customizable. For one thing because of their semantics and for another because they are quite opinionated. Adjustments should be discussed in any case, because there is a lot to consider with these variables in contrast to the ones above.
$color-success
rgb 37|163|66
This is written in $font-color-success
$color-warning
rgb 255|180|0
This is written in $font-color-warning
$color-danger
rgb 220|53|69
This is written in $font-color-danger
To ensure the best possible legibility, we always try to stick to the contrast recommended by the WCAG. However, this is not fully possible with the status colors, since these colors are also assigned a semantic meaning.
A little excursion into color theory: The contrast of yellow to white, for example, can never be 4.5 to 1. If you darken yellow until the desired contrast is achieved, it is no longer yellow but rather an ochre brown - at best a dirty orange. The semantic meaning - yellow as a warning color - is more important in this case than the contrast ratio. Our compromise, which we make for the status colors, is that there is a difference between background colors and text colors. With background colors, we pay more attention to semantic correctness. With text colors, however, we pay more attention to good legibility and a sufficient contrast.
$color-gray-20
rgb 51|51|51
$color-gray-33
rgb 85|85|85
$color-gray-46
rgb 118|118|118
$color-gray-60
rgb 153|153|153
$color-gray-80
rgb 204|204|204
$color-gray-87
rgb 222|222|222
$color-gray-95
rgb 241|241|241
The number of the variable reflects the respective brightness-value from the HSB color model (Hue, Saturation, Brightness) (0 = black, 100 = white).
Each variable is mapped to two classes. The class name is always composed according to the same schema:
.wui-color-- or .wui-bg-color-- gray- number of brightness (eg. .wui-bg-color--gray-95)
-10
-20
-40
-50 (default)
-60
$color-peach
#FBEBEE
#F7D6DC
#E15D75
#D93452
#982439
$color-yangmei
#FAEAF4
#F4D5E9
#D458A6
#C92E90
#8D2065
$color-pitaya
#F7EDF8
#EFDBF0
#BF70C4
#AF4CB5
#7B357F
$color-fig
#F4EFFA
#E9DFF4
#A57FD4
#8F5FC9
#64438D
$color-plum
#F0F0FB
#E1E1F6
#8888DD
#6A6AD4
#4A4A94
$color-blueberry
#EEEFF9
#DDE0F2
#7682CB
#5463BE
#3B4585
$color-akebi
#ECF2F9
#D8E4F2
#6593CC
#3E78BF
#2B5486
$color-grapes
#EDF2F5
#DAE4EB
#6D94B0
#48799C
#32556D
$color-feijoa
#E6F2F2
#CDE5E4
#379893
#057E78
#045854
$color-apple
#E6F3EF
#CEE6DE
#399B7C
#08825B
#065B40
$color-olive
#E8F3EC
#D1E6D9
#479D65
#19843F
#125C2C
$color-kiwano
#F7EFE6
#EFDFCC
#BD7F33
#AD5F00
#794300
$color-papaya
#FBECE6
#F6D9CD
#DC6936
#D34304
#D34304
$color-cherry
#FBE8E8
#F7D2D2
#DE4A4A
#D61D1D
#961414
The fruit colors could be found on all pages and must also work in combination with a variety of components. Together with the other colors they have a great influence on the look and feel and contribute to the recognizability of wescale.
We have dealt intensively with the various use cases so that the wescale-colors meet our very high requirements:
$color-wescale-blue-light
rgb 78|168|226
$color-wescale-blue-dark
rgb 47|113|186