From notes

diff --git a/MelangeURLs.wiki b/MelangeURLs.wiki
index b52eef0..cbea108 100644
--- a/MelangeURLs.wiki
+++ b/MelangeURLs.wiki

@@ -1,13 +1,17 @@
-#summary One-sentence summary of this page.
+#summary Url scheme in melange
+#labels Contents-Skeleton
 
-= Introduction =
+= URLs in Melange =
 
-Add your content here.
-
-
-= Details =
-
-Add your content here.  Format your content with:
-  * Text in *bold* or _italic_
-  * Headings, paragraphs, and lists
-  * Automatic links to other wiki pages
\ No newline at end of file
+  * First path component is “module” (/gsoc, /gci, /core, /tasks)
+  * Second is “component” (/dashboard, /home, /document)
+  * 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>.
+  * Common patterns live in url_patterns.py
+  * Get parameters are used for things like telling the user that their form was saved correctly
+  * GCI uses Get parameters to determine action in task view.
+  * URLs are registered with DjangoUrlPatterns during frontend instantiation
+  * See each module’s callback.py module
+  * MapReduces live at some /_ah/mapreduce “special” url.
+  * AppEngine ensures that only app developers can reach those urls.
\ No newline at end of file