in theory....

if you carefully analyze the entire template ....


it should be possible to somehow cache everything in a single DB entry

then whatever would modify them, would be updated to call an "update cache" function that would rebuild the template



not sure what form the DB entry would take though

raw html?
individual elements?
sections?
one row?
many rows?
serialize?



performance impact of generating the cache?

performance impact of using the cache?