Work towards #56: Splitting up the README

I did the job and splitted up the readme, hopefully everything was
splitted correctly...

flux/index.md

@@ -0,0 +1,18 @@
+---
+layout: pattern
+title: Flux
+folder: flux
+categories: pattern_cat
+tags: pattern_tag
+---
+
+**Intent:** Flux eschews MVC in favor of a unidirectional data flow. When a
+user interacts with a view, the view propagates an action through a central
+dispatcher, to the various stores that hold the application's data and business
+logic, which updates all of the views that are affected.
+
+![alt text](./etc/flux.png "Flux")
+
+**Applicability:** Use the Flux pattern when
+
+* you want to focus on creating explicit and understandable update paths for your application's data, which makes tracing changes during development simpler and makes bugs easier to track down and fix.