-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsmaccs
73 lines (65 loc) · 1.67 KB
/
smaccs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
# CATEGORIES
Base
icon
tag
font
print
Layout
Module
sub-modules
State
media-query
pseudo-class
class name
State Rules
Changing State
animation
Theme
# CSS rules order
Box
Border
Background
Text
Other
# RULES
use class name to distinct element
minimmize de depth
use "layout-"
use "theme-"
use "is-"
use "nav-site"
use "nav-content"
use "stacked"
# Here are some guidelines on how to separate the files in your project:
• Place all Base rules into their own file.
• Depending on the type of layouts you have, either place
all of them into a single file or major layouts into
separate files.
• Put each module into its own file.
• Depending on size of project, place sub-modules into
their own file.
• Place global states into their own file.
• Place layout and module states, including media queries
that affect those layouts and modules, into the module
files.
# GOAL
1. Increase the semantic value of a section of HTML and
content
2. Decrease the expectation of a specific HTML structure
# Goals of a prototype
show states
review localization
isolate dependencies
# Useful features of a preprocessor
Preprocessors offer up plenty of interesting features that can help
make authoring CSS easier. A few of them are:
Variables
Operations
Mixins
Nesting
Functions
Interpolation
File importing
Extending
# preprocessor
The extensions are limited to simple selectors.