2200cde988
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
30 lines
815 B
SCSS
30 lines
815 B
SCSS
#docfy-demo-preview-main-nav-vertical {
|
|
.main-nav-vertical {
|
|
@extend %main-nav-vertical;
|
|
}
|
|
.main-nav-vertical li.hoisted {
|
|
@extend %main-nav-vertical-hoisted;
|
|
}
|
|
.main-nav-vertical .with-intent > * {
|
|
@extend %main-nav-vertical-action-intent;
|
|
}
|
|
.main-nav-vertical .custom-active > * {
|
|
@extend %main-nav-vertical-action-active;
|
|
}
|
|
.wrapper {
|
|
/* a transform is required to mark this element as the containing block */
|
|
/* for hoisting, otherwise the viewport is the containing block */
|
|
transform: translate(0, 0);
|
|
background-color: rgb(var(--tone-gray-600));
|
|
padding-top: 64px;
|
|
}
|
|
// TODO: Reduce the need for these debug overrides
|
|
.main-nav-vertical {
|
|
position: static;
|
|
height: auto;
|
|
}
|
|
.main-nav-vertical ul {
|
|
margin-bottom: 0 !important;
|
|
}
|
|
}
|