Deployed 47675270 to v4.0.0-rc.1 with MkDocs 1.1.2 and mike 0.5.5

latest/extensions/guides/main-extension/index.html

@@ -622,6 +622,30 @@
   </li>
 
         
+          
+          
+          
+
+
+  <li class="md-nav__item">
+    <a href="../generator/" class="md-nav__link">
+      Generator
+    </a>
+  </li>
+
+        
+          
+          
+          
+
+
+  <li class="md-nav__item">
+    <a href="../working-with-mobx/" class="md-nav__link">
+      Working with mobx
+    </a>
+  </li>
+
+        
       </ul>
     </nav>
   </li>
@@ -785,6 +809,18 @@
       
 
 
+  <li class="md-nav__item">
+    <a href="../../../support/" class="md-nav__link">
+      Support
+    </a>
+  </li>
+
+    
+      
+      
+      
+
+
   <li class="md-nav__item">
     <a href="../../../faq/" class="md-nav__link">
       FAQ
@@ -870,7 +906,7 @@
   <span class="p">}</span>
 <span class="p">}</span>
 </code></pre></div>
-<p>There are two methods that you can implement to facilitate running your custom code. <code>onActivate()</code> is called when your extension has been successfully enabled. By overriding <code>onActivate()</code> you can initiate your custom code. <code>onDeactivate()</code> is called when the extension is disabled (typically from the <a href="">Lens Extensions Page</a>) and when implemented gives you a chance to clean up after your extension, if necessary. The example above simply logs messages when the extension is enabled and disabled. Note that to see standard output from the main process there must be a console connected to it. This is typically achieved by starting Lens from the command prompt.</p>
+<p>There are two methods that you can implement to facilitate running your custom code. <code>onActivate()</code> is called when your extension has been successfully enabled. By implementing <code>onActivate()</code> you can initiate your custom code. <code>onDeactivate()</code> is called when the extension is disabled (typically from the <a href="">Lens Extensions Page</a>) and when implemented gives you a chance to clean up after your extension, if necessary. The example above simply logs messages when the extension is enabled and disabled. Note that to see standard output from the main process there must be a console connected to it. This is typically achieved by starting Lens from the command prompt.</p>
 <p>The following example is a little more interesting in that it accesses some Lens state data and periodically logs the name of the currently active cluster in Lens.</p>
 <div class="highlight"><pre><span></span><code><span class="kr">import</span> <span class="p">{</span> <span class="nx">LensMainExtension</span><span class="p">,</span> <span class="nx">Store</span> <span class="p">}</span> <span class="nx">from</span> <span class="s2">&quot;@k8slens/extensions&quot;</span><span class="p">;</span>
 
@@ -1016,7 +1052,7 @@
       <script>
         app = initialize({
           base: "../../..",
-          features: ['navigation.instant', 'toc.autohide', 'search.suggest', 'search.highlight'],
+          features: ['toc.autohide', 'search.suggest', 'search.highlight'],
           search: Object.assign({
             worker: "../../../assets/javascripts/worker/search.0f64ce30.min.js"
           }, typeof search !== "undefined" && search),