Jun 22, 2004 WordPress:
One step backwards, two steps forward
I decided to ditch WordPress for the rest of the site, and keep it just for the journal. I suddenly started to worry about the number of database accesses for very static content, and replaced WordPress with my own tool — which is using mostly static content and no database at all.
In essence, I’m reversing my decision after two days in action. Should I spend more time designing and planning the site instead of hitting in the action? Nah.
I got also more flexibility in the bargain, as I can freely arrange pages and chapters, without needing to hack anything in the WordPress templates. Now I must have a cut-n-paste exercise to get the content to the new pages.
1. Stuart — Tuesday, Jul 27 2004
Not sure if you have any “date moderation” but I’ll carry on anyway. I’m surprised you haven’t had comments on your WP posts. WP users are usually pretty keen on putting their own 2 cents worth when it comes to their favourite blogging tool. Anyhow my site was around for a while before I came to WP so I have an absolute load of static pages. Once I did start using WP I considered which way to go with these. As it turns out my only concession to WP has been to use a PHP include on the static pages for the menu which is great cuz I don’t have to go through them all when I add or remove an item. I have very recently re-designed my Blog layout but have kept it unique to the Blog and one or two Blog related pages such as my Blog Stats, Feed Reader and Archives which uses the “Nicer Archives” plugin. I’ve had a look at the various “Static” plugins that have turned up but haven’t seen anything yet which might make life easier so at the moment my Blog seems to be taking a course of it’s own. Not sure if that’s the right way to go but that’s the way it is for the moment.