Switch to explicitly custom green so we don't have to figure out conflict/sharing/something with Bulma green
The whole override thing, like i need to override their green every time i bring in their initial variables or something? That's a drag.
This commit is contained in:
parent
b0abc26b67
commit
d5bd8737bd
2 changed files with 4 additions and 4 deletions
|
@ -24,7 +24,7 @@
|
|||
|
||||
// Give us some color classes
|
||||
.green {
|
||||
color: $green;
|
||||
color: $geo-green;
|
||||
}
|
||||
|
||||
.yellow {
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
$blue: #4391E0;
|
||||
$red: #a70c20;
|
||||
$light-green: #65AB1F;
|
||||
$green: #478D00;
|
||||
$geo-green: #478D00;
|
||||
$green-gray: #8FB489;
|
||||
$offwhite: #F8F8F8;
|
||||
|
||||
|
@ -14,13 +14,13 @@ $brown: #AD7442;
|
|||
$yellow: #ffdd57;
|
||||
|
||||
// A color for each content type
|
||||
$article: $green;
|
||||
$article: $geo-green;
|
||||
$blog: $blue;
|
||||
$collection: $brown;
|
||||
$gleaning: $yellow;
|
||||
|
||||
// Update Bulma's global variables.
|
||||
$primary: $green;
|
||||
$primary: $geo-green;
|
||||
|
||||
$mini: 363px;
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue