[8ig8]

Regarding WordPress, the author says:

> The theme for the blog and two static pages took up 12 files of HTML and PHP layouts. Furthermore I had made several hacks to make things be just the way I wanted.

I know WordPress is an easy target on some fronts, but this point seems like a stretch. Twelve files plus hacks?

I don't know all your site requirements, but 2 to 4 WP theme files would probably work for what I see on your site.

I'd be interested to see what the twelve files included. I'm no expert but maybe I could offer some tips for simplifying things?

[bem]

I guess I should elaborate on my statement about Wordpress because it came out wrong. I realize Wordpress is powerful, extremely powerful. What I meant was that this comes at an expense. This power means one has to deal with a very extensive API. This is great for someone who needs it (or knows it), but when building a personal site, dealing with an API requiring more than a couple of pages of documentation seems wrong (to me). Something like having to keep af functions.php with a 20+ sloc function to generate the current page title.

Obviously Wordpress does not suck, it is one of the most used blogging platforms. The feeling I got when tweaking it to do something different from the standard themes was that I was using a chainsaw to slice a loaf of bread. It was certainly powerful enough and it could certainly get the job done, but it wasn't easy and it wasn't elegant.

And here is an overview of the files in my custom wordpress theme: http://dl.dropbox.com/u/3240627/wordpress_folder_structure.p... :)