M docs/H3_DeveloperGuide.htm → docs/H3_DeveloperGuide.htm

@@ -7517,7 +7517,7 @@ <p>A route component is a top-level component that handles a route. Unlike ordinary components, route components:</p>
 
 <ul>
 <li>may have a dedicated <em>setup</em> (after the route component is added to the DOM) and <em>teardown</em> phase (after the route component is removed from the DOM and before the new route component is loaded).</li>
-<li>may have built-in local state, initialized during setup and (typically) destroyed during teardown.</li>
+<li>may have built-in local state, initialized during setup and (typically) destroyed during teardown. Such state is passed as the first (and only) parameter of the route component when executed.</li>
 </ul>
 
 
@@ -7768,6 +7768,10 @@ <a name="Next-steps"></a>
 <h3>Next steps<a href="#document-top" title="Go to top"></a></h3>
 
 <p>Made it this far? Good. Wanna know more? Have a look at the code of the <a href="https://github.com/h3rald/h3/tree/master/docs/example">todo list example</a> and try it out <a href="https://h3.js.org/example/index.html">here</a>.</p>
+
+<p>Once you feel more comfortable and you are ready to dive into a more complex application, featuring different routes, route components, forms, confirmation messages, plenty of third-party components etc., have a look at <a href="https://github.com/h3rald/litepad">LitePad</a>. You can see it in action here: <a href="https://litepad.h3rald.com/">litepad.h3rald.com</a>.</p>
+
+<p>Note: the LitePad online demo will store all its data in localStorage.</p>
 
 <a name="API"></a>
 <h2>API<a href="#document-top" title="Go to top"></a></h2>
@@ -8047,7 +8051,7 @@ </ul>
 
     </div>
     <div id="footer">
-      <p><span class="copy"></span> Fabio Cevasco &ndash; June 4, 2020</p>
+      <p><span class="copy"></span> Fabio Cevasco &ndash; June 8, 2020</p>
       <p><span>Powered by</span> <a href="https://h3rald.com/hastyscribe"><span class="hastyscribe"></span></a></p>
     </div>
   </div>

M docs/md/key-concepts.md → docs/md/key-concepts.md

@@ -83,7 +83,7 @@ 
 A route component is a top-level component that handles a route. Unlike ordinary components, route components:
 
 * may have a dedicated *setup* (after the route component is added to the DOM) and *teardown* phase (after the route component is removed from the DOM and before the new route component is loaded).
-* may have built-in local state, initialized during setup and (typically) destroyed during teardown.
+* may have built-in local state, initialized during setup and (typically) destroyed during teardown. Such state is passed as the first (and only) parameter of the route component when executed.
 
 Route components are stll created using ordinary function returning a VNode, but you can optionally define a **setup** and a **teardown** async methods on them (functions are objects in JavaScript after all...) to be executed during each corresponding phase.
 

M docs/md/tutorial.md → docs/md/tutorial.md

@@ -188,4 +188,8 @@ ```
 
 ### Next steps
 
-Made it this far? Good. Wanna know more? Have a look at the code of the [todo list example](https://github.com/h3rald/h3/tree/master/docs/example) and try it out [here](https://h3.js.org/example/index.html).+Made it this far? Good. Wanna know more? Have a look at the code of the [todo list example](https://github.com/h3rald/h3/tree/master/docs/example) and try it out [here](https://h3.js.org/example/index.html).
+
+Once you feel more comfortable and you are ready to dive into a more complex application, featuring different routes, route components, forms, confirmation messages, plenty of third-party components etc., have a look at [LitePad](https://github.com/h3rald/litepad). You can see it in action here: [litepad.h3rald.com](https://litepad.h3rald.com/).
+
+Note: the LitePad online demo will store all its data in localStorage.