Deployed b547541ea to master with MkDocs 1.1.2 and mike 0.5.5

master/contributing/development/index.html

@@ -758,6 +758,19 @@
     Local Development Environment
   </a>
   
+    <nav class="md-nav" aria-label="Local Development Environment">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#developing-on-windows" class="md-nav__link">
+    Developing on Windows
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
         <li class="md-nav__item">
@@ -893,6 +906,19 @@
     Local Development Environment
   </a>
   
+    <nav class="md-nav" aria-label="Local Development Environment">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#developing-on-windows" class="md-nav__link">
+    Developing on Windows
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
         <li class="md-nav__item">
@@ -949,6 +975,8 @@
 <li><code>make dev</code> - builds and starts the app</li>
 <li><code>make clean</code> - cleanup local environment build artifacts</li>
 </ul>
+<h3 id="developing-on-windows">Developing on Windows<a class="headerlink" href="#developing-on-windows" title="Permanent link">#</a></h3>
+<p>On Windows we only support <a href="https://gitforwindows.org/">Git Bash</a> (or similar shell) for running commands.</p>
 <h2 id="github-workflow">Github Workflow<a class="headerlink" href="#github-workflow" title="Permanent link">#</a></h2>
 <p>We Use <a href="https://guides.github.com/introduction/flow/index.html">Github Flow</a>, so all code changes are tracked via Pull Requests.
 A detailed guide on the recommended workflow can be found below:</p>