mirror of
https://github.com/status-im/consul.git
synced 2025-01-09 13:26:07 +00:00
b8166de30d
From an engineers perspective, whenever specifying colors from now on we should use the form: ``` color: rgb(var(--tone-red-500)); ``` Please note: - Use rgb. This lets us do this like rgb(var(--tone-red-500) / 10%) so we can use a 10% opacity red-500 if we ever need to whilst still making use of our color tokens. - Use --tone-colorName-000 (so the prefix tone). Previously we could use a mix of --gray-500: $gray-500 (note the left hand CSS prop and right hand SASS var) for the things we need to theme currently. As we no longer use SASS we can't do --gray-500: --gray-500, so we now do --tone-gray-500: --gray-500. Just for clarity after that, whenever specifying a color anywhere, use rgb and --tone. There is only one reason where you might not use tone, and that is if you never want a color to be affected by a theme (for example a background shadow probably always should use --black) There are a 2 or 3 left for the code editor, plus our custom-query values
34 lines
628 B
SCSS
34 lines
628 B
SCSS
// workaround bulma's sweeping box-sizing
|
|
|
|
%viewport-container {
|
|
box-sizing: content-box;
|
|
}
|
|
%modal-dialog > *,
|
|
%content-container > * {
|
|
box-sizing: border-box;
|
|
}
|
|
%content-container-restricted {
|
|
max-width: 1260px;
|
|
}
|
|
%viewport-container {
|
|
padding-left: 25px;
|
|
padding-right: 25px;
|
|
}
|
|
|
|
fieldset [role='group'] {
|
|
display: flex;
|
|
flex-wrap: wrap;
|
|
flex-direction: row;
|
|
}
|
|
[role='group'] fieldset {
|
|
width: 50%;
|
|
}
|
|
[role='group'] fieldset:not(:first-of-type) {
|
|
padding-left: 20px;
|
|
border-left: 1px solid;
|
|
border-left: rgb(var(--tone-gray-500));
|
|
}
|
|
[role='group'] fieldset:not(:last-of-type) {
|
|
padding-right: 20px;
|
|
}
|