Closed sfrisk closed 8 years ago
One of the questions brought up in today's meeting is do we want to use maps as much as I have in this example, or is it better to split things up more than what I did and have more variables and/or more specific maps.
Perhaps there should be btn-md
and btn-default
modifier classes, instead of setting a default size and color on btn
which then get cascaded and overridden by the existing size and color modifier classes?
@cvrebert +1 we have a goal of avoiding cascading and specificity
yeah, good point. Part of me didn't want to have additional classes, but overwriting is also icky.
http://view.css-chassis.com/96-buttons-take-two/demos/buttons.html @sfrisk a little shadow? The smaller ones look more like labels than buttons.
I'm not entirely thrilled with the design, playing around with it more, just figured I would post what I had so far.
I kind of like the mixins and variables you made. I guess colors/design can wait until we have a few more basic things merged
This branch is now using the palette shown in #140
Ship It. Looks Really Good.!
Button PR has been updated: http://view.css-chassis.com/96-buttons-take-two/demos/buttons.html
Added block buttons, button bar, some hover/active/etc colors for the default button, anchor button demo, and input[type=submit] button demo.
Pinging @geekman-rohit @arschmitz @kristyjy for reviewal. Does this approach look good for buttons and what we wanted for naming conventions?
This looks great to me other than maybe giving the cascading button groups a little more thought. If we do decide to keep the cascading we may want to add notes to the style guide to make sure we have guidelines for deciding when we should and shouldn't cascade.
Update made, removed the need for cascading.
Based on discussions from last week's meeting, here is an initial pass at buttons' variables to help facilitate the discussion on the best practices for organizing and naming variables for jsass.