diff --git a/build/packaged/semantic.min.css.REMOVED.git-id b/build/packaged/semantic.min.css.REMOVED.git-id
index df7e03bef..97fdac3b8 100644
--- a/build/packaged/semantic.min.css.REMOVED.git-id
+++ b/build/packaged/semantic.min.css.REMOVED.git-id
@@ -1 +1 @@
-b3043012b2e87240e84bd8fc6e153fc957640704
\ No newline at end of file
+6e391b4aaddd8f35c92ce70a2fc55635f2c0fd8d
\ No newline at end of file
diff --git a/build/packaged/semantic.min.js.REMOVED.git-id b/build/packaged/semantic.min.js.REMOVED.git-id
index c956842c4..3ca323dc2 100644
--- a/build/packaged/semantic.min.js.REMOVED.git-id
+++ b/build/packaged/semantic.min.js.REMOVED.git-id
@@ -1 +1 @@
-0756a1626ca9d8d5453b31770e15a0f88482c3f9
\ No newline at end of file
+5410fe2c0688f88de7c24d35fd6eda284dc1a8a9
\ No newline at end of file
diff --git a/node/src/documents/specification/cssguide.html b/node/src/documents/specification/cssguide.html
new file mode 100755
index 000000000..199f95b47
--- /dev/null
+++ b/node/src/documents/specification/cssguide.html
@@ -0,0 +1,195 @@
+ ---
+layout : 'default'
+css : 'guide'
+
+title : 'CSS Tips'
+type : 'UI Specification'
+---
+
+
+
Writing CSS
+
Here's a set of guidelines that may help make writing UI components easier.
+
+
+
+
Border box fixes the box model, and allows padding to be included as part of width and height definitions. Using it opens up another world of possibilities for sizing content to fit fluidly
+
+ .ui.two.thingies .ui.thingy {
+ width: 50%;
+ padding: 1em;
+ -webkit-box-sizing: border-box;
+ -moz-box-sizing: border-box;
+ -ms-box-sizing: border-box;
+ box-sizing: border-box;
+ }
+
+
+
+
+
+
Sometimes text can be accidentally highlighted when a user double clicks an element. No need to pull out javascript to solve this.
+
+ .ui.thingy {
+ -webkit-user-select: none;
+ -moz-user-select: none;
+ -ms-user-select: none;
+ user-select: none;
+ }
+
+
+
+
+
+
Sometimes bordered content must sit next to other bordered content. If each element uses border the borders will double. Consider using either outline or a box shadow to accomplish the same effect but without overlapping borders.
+
+ // this might not go so well
+ .ui.thingy {
+ border: 1px solid #DDDDDD;
+ }
+ // rgba is great, but keep in mind the overlapping borders will be added together to create a darker shade
+ .ui.thingy {
+ outline: 1px solid rgba(0, 0, 0, 0.1);
+ }
+ // classic but works
+ .ui.thingy {
+ outline: 1px solid #DDDDDD;
+ }
+ // this works too
+ .ui.thingy {
+ -moz-box-shadow: 0px 0px 0px 1px #DDDDDD;
+ -webkit-box-shadow: 0px 0px 0px 1px #DDDDDD;
+ box-shadow: 0px 0px 0px 1px #DDDDDD;
+ }
+
+
+
+
+
+
It's often useful to have multiple sizes of an element. One tip that makes creating resizes easier is to use EMs and relative EMs or rems.
+
EMs are defined so that 1em is equal to the current font size inside of an element.
+
+ .ui.thingy {
+ font-size: 14px;
+ }
+ // this is 28 pixels
+ .ui.thingy .thing {
+ font-size: 2em;
+ }
+ // woah this is now 48 pixels
+ .ui.thingy .thing .thing {
+ font-size: 2em;
+ }
+
+
+
+
+
+
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
+
+ .ui.menu {
+ font-size: 1rem;
+ }
+ .ui.menu .menu {
+ }
+
+
+
+
+
+
Using EMs however 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.
+
+ .ui.menu {
+ font-size: 1rem;
+ }
+ .ui.menu .menu {
+ margin-left: 0.5em;
+ font-size: 0.9em;
+ }
+
+
+
+
+
+
+
RGBA colors in css allow you to specify colors with a transparency channel. This is very useful.
+
Consider for example, defining the text states of an element. If the elements color changes, the text might appear more complementary as a shade of black with a portion of the original color. This can be done easily with rgba
+
+ .ui.thingy {
+ background-color: #FAFAFA;
+ color: rgba(0, 0, 0, 0.7);
+ }
+ .ui.red.thingy {
+ background-color: #FF0000;
+ }
+
+
+
+
+
+
CSS floats can create issues with the containing element not receiving the size of its children. Using overflow:hidden to clear floats means that no peice of an element can be shown outside the bounding box of the element, which limits the possibilities in an element. Clearfixes can use up one of two available pseudo class which can often be useful for styling elements.
+
Consider using another means of putting content side by side like inline-block or table-cell. These provide more freedom than floated block elements, and can add additional benefits.
+
To avoid issues with inline-block causing spacing between elements, specify no font size on the group and 1rem on the floated content
+
+ // not the best
+ .ui.thingy {
+ display: block;
+ overflow: hidden;
+ }
+ .ui.thingy .part {
+ display: block;
+ float: left;
+ }
+
+ // these do the same thing
+ .ui.thingy {
+ display: block;
+ font-size: 0rem;
+ }
+ .ui.thingy .part {
+ display: inline-block;
+ font-size: 1rem;
+ }
+
+
+
+
+
+
+
One technique that is useful for allowing for infinite color variations of an element, without having to completely reskin each variation and shade, is to use background color and background-image together to define colors.
+
+ .ui.thingy {
+ background-color: #FAFAFA;
+ }
+ .ui.red.thingy {
+ background-color: #FF0000;
+ }
+ .ui.thingy:hover {
+ background-image:
+ -webkit-gradient(linear, 0 0, 0 100%, from(rgba(0, 0, 0, 0.1)), to(rgba(0, 0, 0, 0.05)))
+ ;
+ background-image: -webkit-linear-gradient(
+ rgba(0, 0, 0, 0.1) 0%,
+ rgba(0, 0, 0, 0.05) 100%)
+ ;
+ background-image: -moz-linear-gradient(
+ rgba(0, 0, 0, 0.1) 0%,
+ rgba(0, 0, 0, 0.05) 100%)
+ ;
+ background-image: -o-linear-gradient(
+ rgba(0, 0, 0, 0.1) 0%,
+ rgba(0, 0, 0, 0.05) 100%)
+ ;
+ background-image: linear-gradient(
+ rgba(0, 0, 0, 0.1) 0%,
+ rgba(0, 0, 0, 0.05) 100%)
+ ;
+ }
+
+
+
+
\ No newline at end of file
diff --git a/node/src/documents/specification/styleguide.html b/node/src/documents/specification/styleguide.html
index 9d1e51a56..f105e0a53 100755
--- a/node/src/documents/specification/styleguide.html
+++ b/node/src/documents/specification/styleguide.html
@@ -2,50 +2,111 @@
layout : 'default'
css : 'guide'
-title : 'Style Guide'
+title : 'Authoring Guide'
type : 'UI Specification'
---
-
-
-
-
-
Current status of work on Semantic UI
+
Creating UI Definitions
+
+
Defining anything will involve some slightly arbitrary decision making. The goal of semantic is not to create code that is free from prescription, but to create code that tends to avoid it if possible.
+
The following are some guidelines which help avoid some common pitfalls in writing UI element definitions.
+
+
+
+
Try to use the most obvious names for classes. If you're not sure, prototype the element, then ask a friend or two what they would call it.
+
+ // hmm
+ .ginormous.ui.thingy {
+ font-size: 1.5em;
+ }
+ // better
+ .large.ui.thingy {
+ font-size: 1.5em;
+ }
-
-
-
- HTML
-
-
- Variations should be defined in one word - if its a class then a word exists for it in english
-
-
- Use Border Box
-
- Use gradients for tinting solid colors
-
- Use ems or rems
-
- Use inline block not float
-
- Use after clear fix
-
- Scale content with ems not pixels
-
- Use box shadow instead of borders for adding borders that dont use box model
-
- Use rgba instead of hexcode unless you dont want color layering to be additive
-
-
+
+
+
Classes should be defined in one word, if the concept cannot be reduced to a single word then consider factoring it into multiple sub classes
+
+ .attached.ui.thingy {
+ position: relative;
+ }
+ .left.attached.ui.thingy {
+ left: 0px;
+ top: 50%;
+ margin-top: -0.5em;
+ }
+ .right.attached.ui.thingy {
+ right: 0px;
+ top: 50%;
+ margin-top: -0.5em
+ }
+
+
+
+
+
+
Avoid requiring any specific tags in your definitions. This will allow developers to choose which tags they would like to use with an element.
+
Sometimes however it makes sense to allow for common tags to be used in place of classnames for brevity. Paragraph tags, links, labels, and tables may be useful to use in a UI element definition without classnames.
+
Be cautious though, for example, requiring a form definition to use a form tag limits a developers ability to nest form elements inside other forms. The same is true for anchor tags
+
+
+ // hey how do you know this is the third heading?
+ // and what about all the other possible sizes?
+ .ui.thingy h3 {
+
+ }
+
+ // yay the developer can choose what type of heading tag to use
+ .ui.thingy .header {
+
+ }
+
+ // wow this guy is going to have to do a lot of typing...
+ .ui.table .cell {
+
+ }
+ // this seems like a reasonable assumption, html is a bit strict about these things
+ .ui.table td {
+
+ }
+
+
+
+
+
+ // wow this guy is going to have to do a lot of typing...
+ .ui.table .cell {
+
+ }
+ // this seems like a reasonable assumption, html is a bit strict about these things
+ .ui.table td {
+
+ }
+
+
+
+
+
Elements are often inverted to stand out on dark backgrounds. Consider creating a variation of your element defines how the element can invert its colors.
+
Keep in mind you might have to increase the contrast between shades of your element when inverting colors, its much easier to detect in a design between multiple shades of a light color than a dark one.
+
+ .ui.thingy {
+ background-color: #FFFFFF;
+ color: rgba(0, 0, 0, 0.7);
+ }
+ .ui.inverted.thingy {
+ background-color: #222222;
+ color: rgba(255, 255, 255, 0.7);
+ }
+
+
+
\ No newline at end of file
diff --git a/node/src/layouts/default.html.eco b/node/src/layouts/default.html.eco
index fc97b0143..16ba0ab77 100755
--- a/node/src/layouts/default.html.eco
+++ b/node/src/layouts/default.html.eco
@@ -75,6 +75,14 @@