@@ -28,8 +28,7 @@

     <article>

       <root><section><h1>Routedux — Routes the Redux Way</h1><p>

 <img align="right" alt="Route Dux" src="https://upload.wikimedia.org/wikipedia/commons/thumb/d/da/Ducks_crossing_the_road_sign.png/92px-Ducks_crossing_the_road_sign.png"/></p><p><a href="https://badge.fury.io/js/routedux"><img src="https://badge.fury.io/js/routedux.svg"/></a>

-<a href="https://travis-ci.org/cjdev/routedux"><img alt="Build Status" src="https://travis-ci.org/cjdev/routedux.svg?branch=master"/></a>

-<a href="https://github.com/cjdev/routedux/"><img alt="GitHub stars" src="https://img.shields.io/github/stars/cjdev/routedux.svg?style=flat-square"/></a></p><p>Routedux routes URLs to Redux actions and vice versa.</p><p>Your application doesn't need to know it lives in a browser, but your users want pretty urls and deep links.</p><section><h2>Wait, my application doesn't need to know it lives in a browser?</h2><p>URLs are great for finding things on the internet.  But a single page application is not the same as a collection of

+<a href="https://travis-ci.org/cjdev/routedux"><img alt="Build Status" src="https://travis-ci.org/cjdev/routedux.svg?branch=master"/></a></p><p>Routedux routes URLs to Redux actions and vice versa.</p><p>Your application doesn't need to know it lives in a browser, but your users want pretty urls and deep links.</p><section><h2>Wait, my application doesn't need to know it lives in a browser?</h2><p>URLs are great for finding things on the internet.  But a single page application is not the same as a collection of

 resources that lives on a remote server.</p><p>A single page application is a web application only in the sense that it lives on the web.  URLs are are not essential

 to it working well.</p><p>URLs give users accessing your application in a browser the ability to bookmark a particular view in your application

 so that their expectation of browser-based applications will continue to work.</p><p>We think that's a good thing, but we also don't think the idea of url paths should be littered through your application.</p><p>When you are developing a redux application, you want your UI to be a pure function of the current state tree.</p><p>By adding routes to that, it makes it harder to test.  And this difficulty can be compounded by other decisions about how

@@ -6,7 +6,6 @@

 ◊a[#:href "https://badge.fury.io/js/routedux"]{◊img[#:src "https://badge.fury.io/js/routedux.svg"]}

 ◊a[#:href "https://travis-ci.org/cjdev/routedux"]{◊img[#:alt "Build Status" #:src "https://travis-ci.org/cjdev/routedux.svg?branch=master"]}

-◊a[#:href "https://github.com/cjdev/routedux/"]{◊img[#:alt "GitHub stars" #:src "https://img.shields.io/github/stars/cjdev/routedux.svg?style=flat-square"]}

 Routedux routes URLs to Redux actions and vice versa.