diff --git a/node/src/documents/index.html b/node/src/documents/index.html index c11ee900d..47efcf77a 100755 --- a/node/src/documents/index.html +++ b/node/src/documents/index.html @@ -49,12 +49,12 @@ type : 'Semantic'
-
+
Code
-
+
View
diff --git a/node/src/documents/specification/cssguide.html b/node/src/documents/specification/cssguide.html index e28277a93..b9d78a7c9 100755 --- a/node/src/documents/specification/cssguide.html +++ b/node/src/documents/specification/cssguide.html @@ -108,26 +108,26 @@ type : 'UI Specification'

CSS Legibility

-

Keeping comma separated selectors on separate lines, adding a space after css properties with commasm and always having zeros before a decimal value assist in code legibility.

+

Adding extra formatting can help increase clarity in your code. We suggest separating css selectors on separate lines, adding a space after css properties with commas (like box-shadow) and placing a zero before any decimal value.

// not so easy to read .ui.widgets .widget, ui.widget, .ui.widget.type, ui.widgets .widget.type { color: #FFFFFF; } + // this should have spaces after commas and a zero before any decimal value .ui.widget { - // this should have spaces after the commas and a decimal should aways have a leading zero color:rgba(0,0,0,.3); } - // more legible + // easier to read .ui.widgets .widget, .ui.widget, .ui.widgets .widget.type, .ui.widget.type { color: #FFFFFF; } - // spaces and zeros + // properly formatted .ui.widget { color: rgba(0, 0, 0, 0.3); } @@ -190,7 +190,7 @@ type : 'UI Specification'

Grammatical order

-

Consider using similar class syntax as if you were actually describing the element in english. Although this is by no means required it may help provide clarity in some circumstances.

+

Consider using similar class syntax as if you were actually describing the element in English. Although this is by no means required it may help provide clarity in some circumstances.

// confusing word order .ui.red.button.pointing { @@ -218,7 +218,7 @@ type : 'UI Specification'

Units and Measurements

Relatively Relative

-

EMs are defined so that 1em is equal to the current font size inside of an element. Using EMs can allow you to size content inside an element in proportion to the overall size of the element. Be careful though because this will stack with nested elements

+

EMs are defined so that 1em is equal to the current font size inside of an element. Using EMs can allow you to size content inside an element in proportion to the overall size of the element. Be careful though because this will stack with nested elements.

.ui.thingy { font-size: 14px; @@ -239,7 +239,7 @@ type : 'UI Specification'

Recursively Relative

-

Using EMs multiplicative nature can often be used to your advantage. Instead of defining multiple tiers of a menu system. Consider using ems for its sizing. As you continue to nest menu elements each nested menu will computer its values with smaller proportions.

+

Using EMs multiplicative nature can be used to your advantage. Instead of defining multiple tiers of a menu system, consider using ems to reduce each tier's sizing. As you continue to nest menu elements each nested menu will computer its values with smaller proportions.

.ui.menu { font-size: 1rem; @@ -251,7 +251,7 @@ type : 'UI Specification'

Absolutely Relative

-

REMs are defined so that 1rem is equal to 1 em on the html tag of the page. This is needed to explain how content should be sized related to the overall size of elements on the page

+

Relative EMs (rems) are calculated relative to the font size of the entire page. This is needed to explain how content should be sized related to the overall size of elements on the page, and will not increase geometrically when nested like EMs.

// i am a weird page with very tiny fonts html { @@ -265,6 +265,10 @@ type : 'UI Specification' .ui.menu .menu { font-size: 0.8em; } + // i am the same size as the rule above + .ui.menu .menu .menu { + font-size: 0.8em; + }