summaryrefslogtreecommitdiff
path: root/docs/narr/extending.rst
diff options
context:
space:
mode:
authorJoe Dallago <jd.dallago@gmail.com>2011-03-24 23:38:27 -0500
committerJoe Dallago <jd.dallago@gmail.com>2011-03-24 23:38:27 -0500
commit758464303c00de745672d6c3e27566e3bc52859e (patch)
tree5d369776bfcc601734a20dfb976ed0852b8610a1 /docs/narr/extending.rst
parent95e799d074de2e81914d513b4c331df1e738c00e (diff)
downloadpyramid-758464303c00de745672d6c3e27566e3bc52859e.tar.gz
pyramid-758464303c00de745672d6c3e27566e3bc52859e.tar.bz2
pyramid-758464303c00de745672d6c3e27566e3bc52859e.zip
It was decided that pyramid would undergo a terminology change.
'Paster templates' will now be refered to as 'scaffolds,' while 'rendered templates' will remain as 'templates.' I have changed the docs to reflect this change in terminology.
Diffstat (limited to 'docs/narr/extending.rst')
-rw-r--r--docs/narr/extending.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/extending.rst b/docs/narr/extending.rst
index 416207584..9c96fd605 100644
--- a/docs/narr/extending.rst
+++ b/docs/narr/extending.rst
@@ -191,7 +191,7 @@ The general pattern for extending an existing application looks something
like this:
- Create a new Python package. The easiest way to do this is to create a new
- :app:`Pyramid` application using the "paster" template mechanism. See
+ :app:`Pyramid` application using the scaffold mechanism. See
:ref:`creating_a_project` for more information.
- In the new package, create Python files containing views and other