I am about to start the process of moving my website from Expression Engine back to WordPress. The export process is somewhat involved, so I will be
disabling comments disabling comments for older posts until I get everything moved over and functioning again. Expect to see some hiccups over the next few days!
Why move back to WordPress? I have the choice of upgrading to Expression Engine 2.0, which features a new codebase that is built on the well-regarded PHP Framework CodeIgniter. I’ve actually used CodeIgniter for a bit, and it’s a pretty nifty framework that I’d probably visit again. In fact, it would make a lot of sense for me to put the effort into moving everything to EE 2.0 and reap the many hundreds, perhaps thousands, of benefits that the new system brings. It’s been under development and user preview for a couple of years, and I can testify that the community is very active with great support. That’s what brought me to try Expression Engine in the first place, in addition to its integration with world-class forum and wiki modules under a common user management interface. If I were building a community empire or needed a content management system for a company, I’d certainly strongly consider basing it on Expression Engine.
And that’s the reason I’m switching back to WordPress. When I first made the jump from WordPress 1.6x to Expression Engine, it was because I thought the direction I was going in required the management of a community of users, features, and services. Therefore, I wanted a single user management system for good wiki and forum software. Recently, though, I’ve come to realize that I really don’t want that at all. I’d rather just be writing about stuff that catches my eye, not managing forums or building a content management strategy. I want to move fast, and I want to make things happen now. On top of that, I’ve never liked the blogging environment in Expression Engine. It lacks the workflow niceties that WordPress has: auto-saving, easy updating of the base system, and a more writer-friendly user interface. There have been, I know, many improvements in EE 2.0’s interface, but I haven’t seen anything compelling to keep me.
There are also three technical reasons related to the switch back to WordPress. The caching mechanism makes more sense for the kind of content formatting I do. The templating system is much more gratifying for change junkies like myself. The URL structure is more straightforward. And doing security upgrades is much easier. Or so I imagine. We’ll see how I feel in a few weeks.