Stubbed out readmes.

README.md

@@ -10,11 +10,17 @@ The easiest way to demonstrate a specific architecture/library, is to isolate it
 
 Each module will be tested as much as it can be. This may include a mix of unit tests and UI tests.
 
+You can find modules that explain:
+
+* [MVP](/todo-mvp)
+* [MVVM](/todo-mvvm)
+* [CORE](/core) which contains shared code.
+
 ## Sample
 
 While the title of this gif says 'MVP', this is what you can expect the todo list app in each module to look like. A landing page with a list of sample items, a floating action button that leads to an add task screen, where you can enter the task and be sent back to the main screen. 
 
-<img src="/images/sample.gif" style="height: 640px; width: 400px;">
+You can view the sample [here](/images/sample.gif).
 
 ## Contributions / Requests
 

core/README.md

@@ -0,0 +1,5 @@
+# CORE
+
+This module contains any core code that affects more than one of the individual models. That includes mostly the activity layouts that are the same in each module. 
+
+We want to emphasize the different architecture patterns, and not clutter each module with repeated XML files, or model classes, that appear in each one.

todo-mvp/README.md

@@ -0,0 +1,5 @@
+# MVP
+
+This module is to demonstrate to Model-View-Presenter pattern.
+
+Blog post to be written.

todo-mvvm/README.md

@@ -0,0 +1,5 @@
+# MVVM
+
+This module demonstrates the Model-View-ViewModel architecture pattern.
+
+Blog post to be written.