Status update: I think we're at a breaking point here, y'all. I've designed and coded and tweaked templates for all sorts of views and archives, and sketched out wireframes for a bunch more. It's helped immensely to think of this site as a real design project unto itself: defining goals, doing a mini card sort of the stuff I want to include, and then creating Sharpie-in-notebook wireframes and sketches for the visual design. I've also gone fairly gung-ho with standards-compliant code and Movable Type tricks, so all in all the past 36 hours of furious coding, loading, and rebuilding.

Rebuilding: the bane of existence. There are arguments for MT generating static HTML pages—search engine compatability, lightened server load for high-traffic sites, faster turnaround for the reader. But c'mon, guys, do I really need to wait for 87 entries to rebuild every time I want to tweak the individual entry template?

In fact, I struggled for two hours with a "Premature end of script headers: mt/mt.cgi" error in the middle of wrestling with the individual entry templates, dissecting my template, matching it up against the default template, removing plugins, until I finally came across this logical explanation about scrip timeouts and what-not. Eventually I settled for changing the EntriesPerRebuild value to 25 instead of the default 40 in the mt.cfg file.

Things that remain:

1. Fix column overflow for short entries or pages
2. Implement photos, recipes, and resources areas (okay, fine, this has subtasks)
3. Design new porfolio
4. Implement new porfolio
5. Start creating content!