in reply to Database driven web content: live or tape?
When you are ready to publish, it runs anything that has changed (I'm pretty sure every row in the database has a flag to let the system know if it has been modified) through the templates to generate static html. This reduces server load and tends to be more more search engine friendly.
This model seems to work well, and I'm sure implementing something along these lines would give you the best of both worlds.
gav^
|
---|