Welcome to the Django Template3d docs¶
Template3d is not recommended for use with production sites. It is still very experimental.
Template minimizing and compiling will aid the Django template rendering mechanism with regards to efficiency. This becoming more significant when the django template caching loader is used in conjunction with template3d. Without the use of template caching, every request to a template will be read from the disk and rendered to the front-end. Template caching however, stores template code into memory for fast access without IO bandwidth. If your templates are smaller, so will your memory usage. Also, smaller templates use less bandwidth and help protect sensitive code from unwanted cut and paste coders.
The repository is Mercurial based and hosted with Bitbucket here.
Template3d is a self-contained package. It is not required to install template3d into your python path. There
is an example_project directory contained in the repository which contains a known working model. After
django-admin.py startproject is executed, the contents of the example_project directory will serve as a drop in replacement for the new project root directory. If you wish to use data from the python directory, the Quick Install tutorial is simple to follow.
It is perfectly acceptable to install template3d, and run it completely out of a project directory, at the same time. There is no conflicting structure in the package.
Here are some reference pages to aid you in learning the entirety of template3d.