Last year at this time, I was thinking about various content management systems for user over at Born Geek (sister site to this blog). I never made a decision, mostly because so many of the available options seemed weak to me. One year later, very little has changed and I'm still looking to migrate the site from the hand-built system I use today to a database driven solution.

Currently, I'm leaning towards using WordPress, the same package I use here at this blog. I like the interface that it offers, its documentation is top notch, and I'm already quite familiar with it. The only real downside I can see with the package is that pages are built on the fly. Every month, Born Geek averages 1.56 GB of data transferred, 542,818 hits, and 17,955 unique users. With this much activity on the site, I'm a little concerned about database accesses and the subsequent processor time needed to generate each page. A caching plug-in is available for WordPress, and I hear decent things about it. But will it be enough?

I'm seriously thinking about giving it a try later this winter (converting the site will take some time). So keep your eyes peeled. In the mean time, if you have suggestions for CMS-like systems that might fit the bill, let me know. I'm certainly open to suggestions.