SOme more work.
diff --git a/MelangeURLs.wiki b/MelangeURLs.wiki
index cbea108..fcff0e0 100644
--- a/MelangeURLs.wiki
+++ b/MelangeURLs.wiki
@@ -3,8 +3,20 @@
= URLs in Melange =
- * First path component is “module” (/gsoc, /gci, /core, /tasks)
- * Second is “component” (/dashboard, /home, /document)
+== What does a URL look like? **
+
+ Example: hostname/*gsoc*/*homepage*/*google*/*gsoc2013*
+
+ * The first path component is considered the “module” (examples are /gsoc, /gci, /tasks)
+ * */gsoc* are the Google Summer of Code related urls
+ * */gci* are the Google Code-in related urls
+ * */tasks* are all the Google Appengine TaskQueue related URLs, these are followed by another component to indicate which module they belong to. All urls starting with /tasks can only be hit by a AppEngine developer or an internal AppEngine generated request.
+ * Second is “component”, this indicates the different items and concepts in Melange. This component might be repeated. Examples are:
+ * */dashboard* the dashboard for users
+ * */home* the homepage of the program
+ * */document* any documents in the program
+ * */admin* the administration pages for Hosts
+ * */org/application* organization applications
* Third is “function” or “action”, (sometimes omitted) (“edit”, “show”, “create”, “update”)
* Under what conditions does this appear? If it’s a document, “edit” and “show” will probably appear... but there’s not really consistent criteria
* Fourth path component is ID, keyname, or enough of the key name to unambiguously identify the viewed entity prefixed by /<sponsor>/<program>.
