Actually, the default code will result in an unexepected behavior: the `$color` map is defined in `derived-variables.sass` before setting the custom colors.
IMHO the lists and maps should be defined in a dedicated sass file to avoid confusion in customisation.
For this customization to work, need to add more partial scss files as above
$addColors: (
"twitter":($twitter, $twitter-invert),
"linkedin": ($linkedin, $linkedin-invert),
"github": ($github, $github-invert)
)
$colors: map-merge($colors, $addColors)
Otherwise it failed in my sass build
* Addition of Sass Color Map to Customize Page
Added verbiage to Customization page to demonstrate how to add new colors to the color map.
Using this methodology allows for the dev to use `<i class="fa fa-github has-text-github"></i>` or use `is-github` in a class for a background.
* Change map-merge of $color to only merge once, Sass Complience
- Changed map-merge of $color to import from another map rather than adding each line individually.
- Made it Sass Compliant
Updating based on #1394 comments from @jgthms
* Replace variables.json with colors.json and update related files accordingly
* Add variables data files
* Update variables include template and all related files to use new variables data
* Fix mobile breakpoint id typo in responsivness docs page
* Fix Liquid syntax error in made-with-bulma docs page
* Update bulma sass files count in modular docs page
* Use breakpoints data in responsiveness helpers docs page
* Use breakpoints and variables data in typography helpers docs page
* Add missing page titles in docs pages front matter
* Add breakpoints variables in responsivness docs page
* Update breakpoints list values by looping through page.breakpoints
* Add link to responsiveness variables repo file
* Add mixins variables in responsivness docs page
* Update mixins list values by looping through page.mixins
* Add link to responsiveness mixins repo file
* Update responsivness demo table header
* Add responsivness variables reference table
* Add variables to repo files urls (dry)
* Add breakpoints as jekyll data
* Use responsiveness breakpoints from jekyll data
* Replace breakpoints.yml with breakpoints.json and update relevant code accordingly
* Update URLs to source files in responsiveness docs page
