summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/project.rst9
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/narr/project.rst b/docs/narr/project.rst
index fc3cac009..1b98271fb 100644
--- a/docs/narr/project.rst
+++ b/docs/narr/project.rst
@@ -971,13 +971,16 @@ named ``views`` instead of within a single ``views.py`` file, you might:
- Create a ``views`` directory inside your ``myproject`` package directory
(the same directory which holds ``views.py``).
-- *Move* the existing ``views.py`` file to a file inside the new ``views``
- directory named, say, ``blog.py``.
-
- Create a file within the new ``views`` directory named ``__init__.py``. (It
can be empty. This just tells Python that the ``views`` directory is a
*package*.)
+- *Move* the existing ``views.py`` file to a file inside the new ``views``
+ directory named, say, ``blog.py``. The template :term:`asset
+ specification`s in ``blog.py`` must now be fully qualified with the
+ project's package name (``myproject:templates/blog.pt``) since the
+ ``templates`` directory remains in the ``myproject`` package.
+
You can then continue to add view callable functions to the ``blog.py``
module, but you can also add other ``.py`` files which contain view callable
functions to the ``views`` directory. As long as you use the