diff --git a/GSoC2011GUIOverhaul.wiki b/GSoC2011GUIOverhaul.wiki
index 9e844e4..f0ea3d0 100644
--- a/GSoC2011GUIOverhaul.wiki
+++ b/GSoC2011GUIOverhaul.wiki
@@ -30,7 +30,28 @@
  * Django view (app/soc/views/dashboard.py). Classes in this view are not supposed to be instantiated directly, where each class acts as a base class. To implement iconic dashboard at least one derived class must be created.
  * Djano template (app/soc/templates/v2/soc/dashboard/*)
 
-Lets say you want a GSoC view named dummy_dashboard (which is in app/soc/modules/gsoc/views/dummy_dashboard.py) implements iconic dashboard. First you need to import the base class of dashboard:
+Don't be confused with a dashboard page (participant dashboard and admin dashboard) and the iconic dashboard itself. To avoid the confusion, let's say iconic dashboard is a helper in form of view and template that used by dashboard page, such as participant dashboard and admin dashboard in gsoc module.
+
+It will be easy if we have an example of implementation. Lets say we want a GSoC view named dummy_dashboard (which is in app/soc/modules/gsoc/views/dummy_dashboard.py) implements iconic dashboard with following requirements of links:
+
+ * *"A"*, with description *"This is the first link"* and has two children:
+   * *"A-1"* with description *"Lookup profile page"* and links to lookup page
+   * *"A-2"* with desctiption *"This is actually a link to another dashboard containing two links that appear at the bottom of this description if you set the dashboard in the view correctly"* and has two children:
+     * *"A-2-1"* with description *"bla bla bla"* and links to lookup page
+     * *"A-2-1"* with description *"bla bla bla"* and links to lookup page
+ * *"B"*, with description *"This is the second link"* and has two children:
+   * *"B-1"* with description *"List of my todos"* and links to a dashboard where my todos will be listed in.
+   * *"B-2"* with description *"List of my todos"* and links to a dashboard where my todos will be listed in.
+
+In iconic dashboard implementation, *"A"* and *"B"* considered as both links and dashboard (because *"A"* and *"B"* have children, hence it acts as dashboard/container for their children). The root/main dashboard must be defined in the view to act as a container for both *"A"* and *"B"*, let's name it *MainDashboard*. This is not a must, but it will make life easier later if we name a dashboard class with "Dashboard" suffix. From our requirements aboove, there are five dashboards:
+
+ # DashboardA(Dashboard)
+   # DashboardA2(Dashboard)
+ # DashboardB(Dashboard)
+   # DashboardB1(Dashboard)
+   # DashboardB1(Dashboard)
+
+*"B-1"* and *"B-1"* have no child, but they contain list. So either it has children or list, declare it as a dashboard. All classes must be derived from Dashboard. To import the base class of dashboard:
 
 {{{
 ...
@@ -49,6 +70,8 @@
 ...
 }}}
 
+blabla
+
 Given use cases of GSoC program below on how to alter the dashboard will give you an understanding how the dashboard works.
 
 == Iconic Dashboard Use Case in Admin Dashboard (GSoC) ==