John Cowen b8166de30d
ui: Replaces almost all remaining instances of SASS variables with CSS (#11200)
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
2021-10-07 19:21:11 +01:00

29 lines
590 B
SCSS

@import './skin';
a[rel*='external']::after {
@extend %with-exit-icon, %as-pseudo;
margin-left: 8px;
}
%main-content label a[rel*='help'] {
color: rgb(var(--tone-gray-400));
}
%main-content a[rel*='help']::after {
@extend %with-info-circle-outline-icon, %as-pseudo;
opacity: 0.4;
}
%main-content h2 a {
color: rgb(var(--tone-gray-900));
}
%main-content h2 a[rel*='help']::after {
font-size: 0.65em;
margin-top: 0.2em;
margin-left: 0.2em;
}
.tab-section > p:only-child [rel*='help']::after {
content: none;
}
%main-content p a,
%main-content dd a {
@extend %anchor;
}