summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorianb <devnull@localhost>2005-05-16 03:20:34 +0000
committerianb <devnull@localhost>2005-05-16 03:20:34 +0000
commite8c47309821205d08c4e552169ed80ff782c7411 (patch)
treed60f17cae7cf27f3772c7e6cfe5069ef7c903c69 /docs
parent5bac0516084aac41c49e7dfbbb7fc4f18c1382f4 (diff)
downloadpaste-e8c47309821205d08c4e552169ed80ff782c7411.tar.gz
Added more text
Diffstat (limited to 'docs')
-rw-r--r--docs/blog-tutorial.txt35
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/blog-tutorial.txt b/docs/blog-tutorial.txt
index 6a23f30..bb36f86 100644
--- a/docs/blog-tutorial.txt
+++ b/docs/blog-tutorial.txt
@@ -324,6 +324,41 @@ Now we should be able to run py.test:
Very good! Alright then, on to making an application...
+Static Publishing
+-----------------
+
+Remember I said something about static publishing? So... what does
+that mean?
+
+Well, it means that when possible we should write files out to disk.
+These files might be in their final form, though in some environments
+it might be nice to write out files that are interpreted by `server
+side includes <http://httpd.apache.org/docs/mod/mod_include.html>`_ or
+PHP.
+
+By generating what is effectively code, the "static" files can contain
+dynamic portions, e.g., a running list of recently-updated external
+blogs. But more importantly, many changes can be made without
+generating the entire site; changes to the look of the site, of
+course, but also smaller things, like up-to-date archive links on the
+sides of pages and other little bits of code.
+
+This tutorial will work with server-side includes, because they are
+dumb enough that we won't be tempted to push too much functionality
+into them (and we might be able to extract their functionality into
+fully-formed pages); but they'll also save us a lot of work early on.
+If you haven't used server-side includes you can read the document I
+linked too, but you can also probably pick it up easily enough from
+the examples.
+
+URL Layout
+----------
+
+The blog "application" will be available through some URL (which we
+can figure out at runtime). But everything else gets written onto
+disk with some URL equivalent, so that path and URL will have to be
+configurable.
+
The Front Page
--------------