ashutux wrote:
> I find it a bit unconventional though.. Why have a separate apps_name
> ("apps1" for example) directory under template directory of the same
> app, since those templates are anyways going to be used by the only
> app?
> Has this convention appeared just because the way django code is
> written or are there any other advantages that I am not aware of?Search back through the mailing list and you'll find that I originally argued the same thing :) But in practice, provided conventions are adhered to, this way actually works quite well. It's simple and unmagical (all template directories behave exactly the same way) and has been employed at LJWorld.com (birthplace of Django) successfully for a long time. What does need more clarification in the documentation are the conventions used for writing Django apps, but this really has to wait for the APIs to settle with the upcoming 1.0 release. Kieran
