Interfacing Carefully
-UI definitions in Semantic are given the class name ui. This is to help tell the difference between ui elements and parts of the definition of an element. For example a menu may have menu items inside of it. These items are contained as part of the menu definition but do not receive the class name ui.
UI definitions in Semantic are given the class name ui. This is to help tell the difference between ui elements and parts of the definition of an element. This means any element with the class name UI has a corresponding UI definition.
+
+
For example a menu may have menu items inside of it. These items are contained as part of the menu definition but do not receive the class name ui because they are part of a UI menu collection.
Namespacing
Class names in semantic always use single english words. If a class name is an adjective it is either a type of element or variation of an element. CSS definitions always define adjectives in the context of a noun. In this way class names cannot pollute the namespace.
diff --git a/node/src/documents/introduction/types.html.eco b/node/src/documents/introduction/types.html.eco index 0365216f3..3181f24ef 100755 --- a/node/src/documents/introduction/types.html.eco +++ b/node/src/documents/introduction/types.html.eco @@ -18,10 +18,10 @@ type : 'UI Introduction'Overview
-A type is a mutually exclusive change to an element. Types may require different html structures to work correctly, or expect different content.
+A type is a mutually exclusive change to an element. Types may require different html structures to work correctly, or expect different content.
Content
-An icon menu might expect you to include glyphs instead of text to be formatted correctly
+For example, an icon menu might expect different content like icons glyphs instead of text to be formatted correctly