-
Notifications
You must be signed in to change notification settings - Fork 0
Improve color variable naming scheme #1
Comments
Looks good to me. What about when using our variables in conjunction with a 3rd party library (e.g. bootstrap). Do we stick to using our own colors and set the 3rd party library variables where appropriate? For example, we define $color-black: #000000;
$color-japanese-laurel: #06a20d;
$color-cinnabar: #e43e33; in our files. Then, in $brand-primary: $color-black and so on? |
@peschee Seems legit! 👍 |
Let's try it. |
@dschenk Good point!
We already have this feature in our styleguide generator, but it’s currently disabled. So we are kind of locked and loaded for this case. |
* release/1.2.0: Remove normalize.css from Aigis styles Improve wording Update dependencies Bump minor version Add release date of 1.2.0 and missing changes Add possibility to define custom sourcePath in styleguide components Drop double variable system for colors. Closes #1 Build all *.scss files, not just styles.scss Add missing links to CHANGELOG Fix typos in CHANGELOG Add 1.2.0 to CHANGELOG Update README about SassDoc Add SassDoc Document sass functions, improve stringify() parameters Improve aigis styles files structure Add duotone-light syntax theme Rename map-stringify function and improve it Add neutral and brighter aigis theme as default
For a long time we’ve been using the double variables system, mostly in order to preserve the ability to easily create a themable stylesheet.
For example all basic colors were stored in variables beginning with
$color-{{name}}: #e43e33;
. Then we created color variables that made the semantic link to the actual color, like this:$color-background-primary: $color-cinnabar;
As I mentioned in the beginning we did that for a long time. By now I'm wondering if that‘s still necessary because I think we can switch to a single naming/variable system and still keep our options open regarding themability. Plus we would lose the tight coupling/chaining of semantic color variables.
So I would propose we handle it like this:
meta/_colors.scss
Yeah, gimme code. I need code.
@gridonic/frontend Can I get a 👍?
The text was updated successfully, but these errors were encountered: