Docs WIP

.idea/codeStyleSettings.xml

@@ -16,5 +16,6 @@
       </value>
     </option>
     <option name="USE_PER_PROJECT_SETTINGS" value="true" />
+    <option name="PREFERRED_PROJECT_CODE_STYLE" value="Default (2)" />
   </component>
 </project>

README.md

@@ -194,10 +194,11 @@ This is the step in which the hiccup-formatted
 "descriptions of required DOM", returned by the view functions of Domino 5, are made real.
 The browser DOM nodes are mutated. 
 
-### Whew! A reprieve
+### As A Picture
+
+
+[]("/images/Readme/6dominoes.png?raw=true")
 
-After the six dominoes have fallen, re-frame (metaphorically) stands them up. 
-Your re-frame app is poised lithely, ready for the next `event` to trigger the cycle again. 
 
 ## A Cascade Of Simple Functions
 
@@ -223,7 +224,7 @@ the last domino which does the dirty work and realises these descriptions.
 In both cases, you don't need to worry yourself about this dirty work. re-frame looks 
 after those dominoes.
 
-## Code Fragments
+## As Code Fragments
 
 Let's take this domino narrative one step further and introduce some code fragments. 
 We're going to be working on a SPA with a list of items.

docs/ApplicationState.md

@@ -1,27 +1,19 @@
-<!-- START doctoc generated TOC please keep comment here to allow auto update -->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-## Table Of Contents
-
-- [Application State](#application-state)
-    - [Table Of Contents](#table-of-contents)
-  - [On Data](#on-data)
-  - [The Big Ratom](#the-big-ratom)
-  - [The Benefits Of Data-In-The-One-Place](#the-benefits-of-data-in-the-one-place)
-  - [Get You A Leveragable Schema](#get-you-a-leveragable-schema)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
-## Application State
-
-How does re-frame manage application state?
+- [On Data](#on-data)
+- [The Big Ratom](#the-big-ratom)
+- [The Benefits Of Data-In-The-One-Place](#the-benefits-of-data-in-the-one-place)
 
 
 #### Table Of Contents
 
+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
+
 - [On Data](#on-data)
 - [The Big Ratom](#the-big-ratom)
 - [The Benefits Of Data-In-The-One-Place](#the-benefits-of-data-in-the-one-place)
 
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
+
 ### On Data
 
 <blockquote class="twitter-tweet" lang="en"><p>Well-formed Data at rest is as close to perfection in programming as it gets. All the crap that had to happen to put it there however...</p>&mdash; Fogus (@fogus) <a href="https://twitter.com/fogus/status/454582953067438080">April 11, 2014</a></blockquote>
@@ -126,7 +118,7 @@ shows how to use a spec.  Look in `src/db.cljs` for the spec itself, and then in
 how to write code which checks `app-db` against this spec after every single event has been 
 processed. 
 
-Specs are leveragable. Watch how: <br>
+Specs are more leveragable than types. Watch how: <br>
 https://www.youtube.com/watch?v=VNTQ-M_uSo8
 
 *** 

docs/EffectfulHandlers.md

@@ -397,6 +397,7 @@ to then, as a next step, better understand coeffects and effects. We'll soon be
 
 ***
 
+Previous:  [Infographic Overview](EventHandlingInfographic.md)      
 Up:  [Index](README.md)      
 Next:  [Interceptors](Interceptors.md)  
 

docs/EventHandlingInfographic.md

@@ -0,0 +1,14 @@
+## An Infographic View Of Event Handling
+
+Three diagrams are provided. The first is a beginners view, 
+the second is a useful schematic, and the third is accurate and detailed.  
+
+View them in conjunction with a reading of the written tutorials. 
+
+[]("/images/event-handlers.png?raw=true")
+
+*** 
+
+
+Up:  [Index](README.md)      
+Next:  [Effectful Handlers](EffectfulHandlers.md)      

docs/README.md

@@ -8,6 +8,7 @@
 
 ### Event Handlers
 
+- [Infographic Overview](EventHandlingInfographic.md)
 - [Effectful Handlers](EffectfulHandlers.md)
 - [Interceptors](Interceptors.md)
 - [Effects](Effects.md)