- Online Prototyping
- User Testing & Feedback
- UI Design Patterns
- Colours & Gradients
- User & Profile Photos
- Stock Photography
- Icons
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
license: mit |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
All arguments *may* be space separated lists: | |
@include link-states(<properties>, <normal values>[, <state values>] | |
[, <:active values>][, <:focus values>]); | |
Example: | |
a { | |
@include link-states(color, red, blue); | |
} | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Principle 1: Classes as selectors, not ids or element tags. | |
CSS classes are best suited to keep the code modular, easy to change and has additional | |
benefits, such as being able to mix styles together. If we've done a good job of building up | |
our styles, it should be very fast to prototype and build out new layouts. | |
The main risk using classes as selectors is the possibility of conflicts if two different | |
classes get the same name. This is where BEM comes in handy with prefixes and naming conventions | |
descriptive enough to prevent this from happening. |