Added client and server architecture details.
diff --git a/GSoC2010DataSeeder.wiki b/GSoC2010DataSeeder.wiki
index f7dc30f..59e9d52 100644
--- a/GSoC2010DataSeeder.wiki
+++ b/GSoC2010DataSeeder.wiki
@@ -308,6 +308,33 @@
 }
 }}}
 
+
+
+= Architecture =
+
+== Client-side ==
+
+There are 2 JavaScript files containing the client-side logic:
+
+  * *app/soc/content/js/melange.seeder-??????.js*
+    * Keeps the metadata about models and providers (which it queries the server for) and providers convenience functions for accessing the data.
+  * *app/soc/content/js/templates/modules/seeder/home-??????.js*
+    * Does everything that happens in the web interface, using the data provided by _melange.seeder-??????,js_. This includes:
+      * Adding models to the web interface and configuring them
+      * Importing existing configuration sheets
+      * Building configuration sheets
+
+== Server-side ==
+
+  * Server side code is in the *soc.modules.seeder* package
+    * *soc.modules.seeder.logic* - contains all the logic for the data seeder
+      * *logic.models* - Takes care of the model introspection part and builds the JSON data sent to the client regarding models.
+      * *logic.providers* - Same as _logic.models_, but handles data providers instead of models.
+      * *logic.seeder* - Handles configuration sheet validation and actually seeding a model given a valid configration sheet.
+      * *logic.mapper* - Takes care of the seeding using the MapReduce function. Defines mapper functions and input readers. Does the splitting of the full configuration sheet into smaller pieces and forwards the seeding job to _logic.seeder_
+    * *soc.modules.seeder.views* - Defines the views used by the seeder. Mostly just reuses code from _soc.modules.seeder.logic_.
+
+
 = Proposed timeline =
 
 == Week 1 (24 May - 30 May) ==