# HG changeset patch
# User Todd Larsen <tlarsen@google.com>
# Date 1210101937 0
# Node ID 962da9e1065d7f248edd188d8563d90e8d81e9ca
# Parent  cc10e920ecea5b105a902f44ae09f9f6330fbfc9
Add a "namespace-subdivided" Django templates directory for the SoC
framework.

diff -r cc10e920ecea -r 962da9e1065d soc/templates/README.templates
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/soc/templates/README.templates	Tue May 06 19:25:37 2008 +0000
@@ -0,0 +1,18 @@
+Templates are placed in a "namespace" subdirectory in the templates directory,
+since the templates directory will be added to the Django templates search
+path.  This allows other packages to extend existing templates without "hiding"
+the original template.  For example, a template in another Melange application
+can extend a template in the SoC framework like this:
+
+  {% extends 'soc/some_existing_template.html %}
+
+without "hiding" the some_existing_template.html for other uses, even if the
+derived template is also named some_existing_template.html.
+
+So, please do not put any templates in this soc/templates directory, but only
+place them in the soc/templates/soc "namespace" subdirectory.
+
+Different Melange applications should also follow this pattern, to promote
+sharing of templates between applications as well.  For exmample, the GSoC
+Melange application should place its templates in gsoc/templates/gsoc.
+