Edited wiki page GSoC2011IntegrationWithExternalAPIs through web user interface.

GSoC2011IntegrationWithExternalAPIs.wiki

diff --git a/GSoC2011IntegrationWithExternalAPIs.wiki b/GSoC2011IntegrationWithExternalAPIs.wiki
index a6882eb..91c66cd 100644
--- a/GSoC2011IntegrationWithExternalAPIs.wiki
+++ b/GSoC2011IntegrationWithExternalAPIs.wiki
@@ -1,9 +1,30 @@
 #summary One-sentence summary of this page.
 #labels gsoc2011,externalapisproject
 
-= Introduction =
+= 1. Introduction =
 
 This page is tracking of progress for GSoC 2011 Project: Integration with External API's
+----
+
+= 2. Requirements =
+== 2.1 Melange Lists ==
+===2.1.1 Overview===
+Basically an export button for each lists on Melange that triggers an export mechanism to Google SpreadSheets. (including OAuth roundtrip, access token storing on datastore)
+===2.1.2 Problems & Solutions===
+ * *Problem:* exporting a JavaScript list
+ * *Solution:* 
+
+== 2.2 Student Proposals ==
+=== 2.2.1 Overview ===
+Students will be able to edit their proposals through tinyMCE editor or link to a Google Document file. There will be a "Sync Now" button to syncronize proposal that Melage holds with actual Google Documents file.
+=== 2.2.2 Problems & Solutions ===
+ * *Problem:* Student may not be awere that proposal is syncronised only when he/she clicks "Sync Now" button.
+ * *Solution1:* Give responsibility to student.
+ * *Solution2:* Sync proposal with stored ACL. Check for single revisions and get the closest revision to deadline.
+
+ * *Problem:* As Google Documents stores HTML files in full-HTML form (including images, css files etc.) a method must be implemented to embed that document to actual proposal entry.
+ * *Solution:* 
+----
 
 = Design & Terminology = 
 == Resource ==
@@ -29,4 +50,4 @@
                                required=True,
                                collection_name='exported_documents',
                                verbose_name=ugettext('Owner'))
-}}}
+}}}
\ No newline at end of file