Last week I enabled dynamic rendering for my individual entry archive pages. If at this point you are shaking your head and thinking, “Whuh?” then, to put it more simply, I flipped the switch on a very cool feature of Movable Type 3.1 and I’m digging it greatly.
The handful of plug-ins I use (like Markdown) have already been ported to work with MT’s dynamic rendering engine (like PHP Markdown) and it was easy to transcribe my own little PHP hacks into full-blown Smarty plug-ins.
kristine wrote:
that’s kinda what I’ve been thinking about doing, making just the individual pages dynamic. I was telling somebody else in comments yesterday, I came up with a lot of general php codes for stuff before Plugins were an options, so I’m not as far behind as I could be. LOL! So yay, I’m glad to hear its working good for you, makes me feel motivated to work on it too :)
Link |
TypeKey Authenticated
September 23, 2004 12:32 AM
tien wrote:
any chance that someone could explain what this does (ie the benefits) in layman’s terms?
Link |
TypeKey Authenticated
September 23, 2004 4:50 AM
Walt wrote:
Well, here are a few of the benefits from my perspective. First, when I rebuild my site with Movable Type, I don’t have to wait for it to rebuild all of my individual entries. And previously, that was the most time-consuming part of a complete site rebuild. Second, it saves disk space on my server since all those files aren’t being written out statically. Finally, (and this is what sets Movable Type apart) I can still get all the benefits of static templates for other templates like my main weblog page and syndication feeds.
Link |
TypeKey Authenticated
September 23, 2004 8:09 AM