@@ -1 +1,2 @@

-To compile this site, you need DrRacket and then you just run `raco pkg install pollen && raco pollen render` from this directory

+To compile this site, you need DrRacket and then you just run `raco pkg install

+pollen && raco pollen render from this directory

@@ -1,32 +1,3 @@

 * {

     box-sizing: border-box;

 }

-

-nav#pagewise {

-    position: relative;

-    width: 100%;

-}

-

-#prev-page, #next-page {

-    position: absolute;

-    width: 48%;

-    z-index: 10000;

-}

-

-#prev-page::after {

-    content: "|";

-}

-

-#prev-page {

-    left: 0;

-    text-align: left;

-}

-

-#next-page {

-    right: 0;

-    text-align: right;

-}

-

-article {

-    position: relative;

-}

@@ -63,7 +63,10 @@ match.  Exact matches are always preferred to wildcards moving from left to righ

   '/user/me/:view',

   '/user/:id/update', // less specific because 'me' is exact match, while :id is a wildcard

   '/user/:id/:view'

-];</code></pre></section><section><h2>Fragment component</h2><pre><code class="javascript"><p>const state = {

+];</code></pre></section><section><h2>Fragment component</h2><p>Given that every UI state will be in your state tree as a function of

+your reducer logic, you can express any restriction on which parts of

+the UI display, even those that have nothing to do with the specific

+transformations caused by your URL actions.</p><pre><code class="javascript"><p>const state = {

   menu: ...

 }</p><p>const view = (

   <PageFrame>

@@ -91,9 +94,15 @@ const view = (

 (

   <PageFrame>

   </PageFrame>

-)</p></code></pre><p>Given that every UI state will be in your state tree as a function of your reducer logic, you can express any restriction

-on which parts of the UI display, even those that have nothing to do with the specific transformations caused by

-your URL actions.</p><p>We have a demo codebase at <a href="https://github.com/cjdev/routedux-docs-demo">demo repository</a>.</p></section></section>

+)</p></code></pre></section><section><h2>ActionLink and pathForAction(action)</h2><p>Occasionally it is nice to render URLs inside of your application.</p><p>As a convenience, we have attached <code class="javascript">pathForAction</code> to the  <code class="javascript">store</code>

+object, which uses the same matcher that the action matcher uses.  This allows you to create links in your application

+by using the actions.</p><pre><code class="javascript"><p>const routesConfig = [

+  ['/user/:id', LOAD_USER, {}],

+  ['/user/me', LOAD_USER, {id: currentUserId()}]

+];

+// ... do store initialization</p><p>store.pathForAction({type:LOAD_USER, id: currentUserId()});</p><p>// returns /user/me</p><p>//  ActionLink</p><p>&lt;ActionLink action={{type:LOAD_USER, id: 123}}&gt;Link Text&lt;/ActionLink&gt;

+// renders as &lt;a href="/user/123"&gt;Link Text&lt;/a&gt;</p></code></pre></section><p>Now you have links, but your links always stay up to date with your

+routing configuration.</p><section><h2>Demo Site</h2><p>We have a demo codebase at <a href="https://github.com/cjdev/routedux-docs-demo">demo repository</a>.</p></section></section>

 </root>

     </article>

     <script>hljs.initHighlightingOnLoad();</script>

@@ -103,6 +103,11 @@ const routesInOrderOfPrecedence = [

 }

 ◊section[#:headline "Fragment component"]{

+Given that every UI state will be in your state tree as a function of

+your reducer logic, you can express any restriction on which parts of

+the UI display, even those that have nothing to do with the specific

+transformations caused by your URL actions.

+

 ◊pre{

 ◊code[#:class "javascript"]{

 const state = {

@@ -145,10 +150,6 @@ const view = (

   </PageFrame>

 )

 }}

-

-Given that every UI state will be in your state tree as a function of your reducer logic, you can express any restriction

-on which parts of the UI display, even those that have nothing to do with the specific transformations caused by

-your URL actions.

 }

 ◊section[#:headline "ActionLink and pathForAction(action)"]{

@@ -166,7 +167,9 @@ const routesConfig = [

 ];

 // ... do store initialization

-store.pathForAction({type:LOAD_USER, id: currentUserId()}); // returns /user/me

+store.pathForAction({type:LOAD_USER, id: currentUserId()});

+

+// returns /user/me

 //  ActionLink

@@ -175,6 +178,9 @@ store.pathForAction({type:LOAD_USER, id: currentUserId()}); // returns /user/me

 }}

 }

+Now you have links, but your links always stay up to date with your

+routing configuration.

+

 ◊section[#:headline "Demo Site"]{

 We have a demo codebase at ◊a[#:href "https://github.com/cjdev/routedux-docs-demo"]{demo repository}.

 }