I have a v9 project WIP and rather than untangling Atomik I am creating a shim that works on top of it. In the process I was disappointed at the lost opportunity for effective use of css variables.
opened 02:46PM - 26 Dec 21 UTC
Type:Enhancement
Status:Proposal
In the Atomik theme, at the top of the theme all colours, fonts and some other a… spects are defined using css variables, for example
`--bs-primary: #2d7ac0;`
The concept is that these constants can then be used throughout the theme, so the theme can be re-skinned by redefining these css constants.
In some places this has been implemented.
`color: rgba(var(--bs-primary-rgb)`
However, in many places this has not been respected. For example, colours originally defined as
`--css-variable-name: #012345;`
rather than being compiled to
```
.classname{
colour: var(--css-variable-name);
}
```
Have in many instances been compiled to
```
.classname{
colour: #012345;
}
```
This means that in many cases colours and other theme aspects that should to be customizable by the CMS design menu or changing a css variable are not universally configurable without recompiling the theme from SASS.