Hi Brandon,
Brandon Taylor wrote:
> Hello everyone,
>
> I'm just getting started, so please bear with me. How should I
> organize my website?
In our project, we use a little bit different source code organization:
/
|-- apps/
| |-- app1/
| |-- app2/
| |-- ...
| |-- special_app/ (special app for common template tags)
|
|-- templates/
| |-- app1/
| |-- app2/
| |-- ...
|
|-- static/
| |-- component1/ (.js and .css files)
| |-- images/
| |-- component2/
| |-- images/
| |-- ...
|-- lib/
|-- (various files like settings.py, urls.py)
Some notes:
* settings.py includes only common (and default) settings.
All personalized data (like db access credentials) is in
the .mysettings.py file that is accessed from the settings.py
* main urls.py simply includes local applications' urls
from apps/app_name/urls.py
* static/ directory is not served by django
* lib/ contains special classes and functions we use
(like text splitter class, useful decorators, etc.)
* initially, we had a different tree under static/ directory.
It was as simple as /images, /stylesheets and /javascripts. But
then we had to reorganize our code and change this directory
accordingly.
* and our code is not in the website root.
Of course, I can't say that our (or somebody's else) source code
organization is the best because it is not. And, I guess, our current
tree is not final even for this particular project I am involved in.
Anton
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
