We’re thinking about a redesign of Seabury’s website based on Moveable Type, and the question arises of whether to allow our design to encompass any pages not generated through the MT engine. The rationale for static pages (in the sense of “designed to be static,” not just “generated once at a rebuild rather than constructed on demand”) would be a greater degree of flexibility with regard to layout and content, and perhaps an easier transition from pages built under our present design schema; the downside would be that the MT search function would not be able to search the “static” pages, and that we’d have two modes of preparing data, one of which constitutes a near-total wild card for the page writer.
The more I think about it, the righter Micah’s advice on the topic sounds: All MT, every page. But I still want to think it over, to make sure I’m not missing some important angle.
By the way, I was this close to changing my Disseminary blog over to WordPress, of which I’ve gotten a generally favorable impression from an experimental site — but at the last minute we got MT 3 working over the smoking rubble of the old installation, and I have to say that the new version provides a very helpful approach to handling unwelcome commercial comments. I haven’t settled all the way in yet, but I like the transition so far.