There should be 10 different tag colors:
1. is-black;
2. is-dark;
3. is-light;
4. is-white;
5. is-primary;
6. is-link;
7. is-info;
8. is-success;
9. is-warning;
10. is-danger;
Just a small mistake I caught, as I was playtesting the framework. :)
* Fix navbar-burger sample code in navbar.html
<button> elements with the class combination of button and navbar-burger display with a border. Updating to divs and removing button class
* Update navbar.html
Fixing button ending tags based on suggestion from @feute
Seems like the current text belong on the ```responsive-helpers``` page and not these generic helpers. I've cut a few words, but a better wording would probably be better.
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
