clean up coding style page

Author: arroyo

docs/help/style-guide.md

@@ -1,6 +1,6 @@
 # Erdiko coding style guide
 
-All of the erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript & Sass).  All code is stored on [Github](https://github.com/erdiko).
+All of the Erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript & Sass).  All code is stored on [Github](https://github.com/erdiko).
 
 Below you will find details on how we write our code.  We do our best to stick to these guidelines.
 
@@ -24,16 +24,14 @@ We follow Google's JavaScript style guide.
 [https://google.github.io/styleguide/jsguide.html](https://google.github.io/styleguide/jsguide.html)
 
 
-## HTML
+## HTML / CSS
 
-We follow Google's HTML style guide as well
+We follow Google's HTML / CSS style guide as well
 
 [https://google.github.io/styleguide/htmlcssguide.html](https://google.github.io/styleguide/htmlcssguide.html)
 
-
-## CSS
-
-
 ## Sass
 
+We adhere to Sass best practices, but we admit there is plenty of room for improvement here as we continue to break apart front-end code into re-usable packages.
+
 [http://sass-lang.com/](http://sass-lang.com/)

site/help/style-guide/index.html

@@ -620,15 +620,8 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#html" title="HTML" class="md-nav__link">
-    HTML
-  </a>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#css" title="CSS" class="md-nav__link">
-    CSS
+  <a href="#html-css" title="HTML / CSS" class="md-nav__link">
+    HTML / CSS
   </a>
 
 </li>
@@ -713,15 +706,8 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#html" title="HTML" class="md-nav__link">
-    HTML
-  </a>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#css" title="CSS" class="md-nav__link">
-    CSS
+  <a href="#html-css" title="HTML / CSS" class="md-nav__link">
+    HTML / CSS
   </a>
 
 </li>
@@ -751,7 +737,7 @@
 
 
                 <h1 id="erdiko-coding-style-guide">Erdiko coding style guide<a class="headerlink" href="#erdiko-coding-style-guide" title="Permanent link">&para;</a></h1>
-<p>All of the erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript &amp; Sass).  All code is stored on <a href="https://github.com/erdiko">Github</a>.</p>
+<p>All of the Erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript &amp; Sass).  All code is stored on <a href="https://github.com/erdiko">Github</a>.</p>
 <p>Below you will find details on how we write our code.  We do our best to stick to these guidelines.</p>
 <h2 id="php">PHP<a class="headerlink" href="#php" title="Permanent link">&para;</a></h2>
 <p>We adhere to the <a href="http://www.php-fig.org/psr/psr-2/">PSR</a> coding style guide.  </p>
@@ -762,11 +748,11 @@ <h2 id="php">PHP<a class="headerlink" href="#php" title="Permanent link">&para;<
 <h2 id="javascript">JavaScript<a class="headerlink" href="#javascript" title="Permanent link">&para;</a></h2>
 <p>We follow Google's JavaScript style guide.</p>
 <p><a href="https://google.github.io/styleguide/jsguide.html">https://google.github.io/styleguide/jsguide.html</a></p>
-<h2 id="html">HTML<a class="headerlink" href="#html" title="Permanent link">&para;</a></h2>
-<p>We follow Google's HTML style guide as well</p>
+<h2 id="html-css">HTML / CSS<a class="headerlink" href="#html-css" title="Permanent link">&para;</a></h2>
+<p>We follow Google's HTML / CSS style guide as well</p>
 <p><a href="https://google.github.io/styleguide/htmlcssguide.html">https://google.github.io/styleguide/htmlcssguide.html</a></p>
-<h2 id="css">CSS<a class="headerlink" href="#css" title="Permanent link">&para;</a></h2>
 <h2 id="sass">Sass<a class="headerlink" href="#sass" title="Permanent link">&para;</a></h2>
+<p>We adhere to Sass best practices, but we admit there is plenty of room for improvement here as we continue to break apart front-end code into re-usable packages.</p>
 <p><a href="http://sass-lang.com/">http://sass-lang.com/</a></p>
 
 

site/mkdocs/search_index.json

@@ -972,12 +972,12 @@
         }, 
         {
             "location": "/help/style-guide/", 
-            "text": "Erdiko coding style guide\n\n\nAll of the erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript \n Sass).  All code is stored on \nGithub\n.\n\n\nBelow you will find details on how we write our code.  We do our best to stick to these guidelines.\n\n\nPHP\n\n\nWe adhere to the \nPSR\n coding style guide.  \n\n\nhttp://www.php-fig.org/psr/psr-2/\n\n\nMore useful PHP-FIG links:\n\n\nhttp://www.php-fig.org/bylaws/psr-naming-conventions/\n\n\nhttp://www.php-fig.org/psr/psr-1/\n\n\nJavaScript\n\n\nWe follow Google's JavaScript style guide.\n\n\nhttps://google.github.io/styleguide/jsguide.html\n\n\nHTML\n\n\nWe follow Google's HTML style guide as well\n\n\nhttps://google.github.io/styleguide/htmlcssguide.html\n\n\nCSS\n\n\nSass\n\n\nhttp://sass-lang.com/", 
+            "text": "Erdiko coding style guide\n\n\nAll of the Erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript \n Sass).  All code is stored on \nGithub\n.\n\n\nBelow you will find details on how we write our code.  We do our best to stick to these guidelines.\n\n\nPHP\n\n\nWe adhere to the \nPSR\n coding style guide.  \n\n\nhttp://www.php-fig.org/psr/psr-2/\n\n\nMore useful PHP-FIG links:\n\n\nhttp://www.php-fig.org/bylaws/psr-naming-conventions/\n\n\nhttp://www.php-fig.org/psr/psr-1/\n\n\nJavaScript\n\n\nWe follow Google's JavaScript style guide.\n\n\nhttps://google.github.io/styleguide/jsguide.html\n\n\nHTML / CSS\n\n\nWe follow Google's HTML / CSS style guide as well\n\n\nhttps://google.github.io/styleguide/htmlcssguide.html\n\n\nSass\n\n\nWe adhere to Sass best practices, but we admit there is plenty of room for improvement here as we continue to break apart front-end code into re-usable packages.\n\n\nhttp://sass-lang.com/", 
             "title": "Coding style guide"
         }, 
         {
             "location": "/help/style-guide/#erdiko-coding-style-guide", 
-            "text": "All of the erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript   Sass).  All code is stored on  Github .  Below you will find details on how we write our code.  We do our best to stick to these guidelines.", 
+            "text": "All of the Erdiko code is broken up into convenient packages that are published on either Packagist (PHP) or NPM (JavaScript   Sass).  All code is stored on  Github .  Below you will find details on how we write our code.  We do our best to stick to these guidelines.", 
             "title": "Erdiko coding style guide"
         }, 
         {
@@ -991,18 +991,13 @@
             "title": "JavaScript"
         }, 
         {
-            "location": "/help/style-guide/#html", 
-            "text": "We follow Google's HTML style guide as well  https://google.github.io/styleguide/htmlcssguide.html", 
-            "title": "HTML"
-        }, 
-        {
-            "location": "/help/style-guide/#css", 
-            "text": "", 
-            "title": "CSS"
+            "location": "/help/style-guide/#html-css", 
+            "text": "We follow Google's HTML / CSS style guide as well  https://google.github.io/styleguide/htmlcssguide.html", 
+            "title": "HTML / CSS"
         }, 
         {
             "location": "/help/style-guide/#sass", 
-            "text": "http://sass-lang.com/", 
+            "text": "We adhere to Sass best practices, but we admit there is plenty of room for improvement here as we continue to break apart front-end code into re-usable packages.  http://sass-lang.com/", 
             "title": "Sass"
         }, 
         {