The great Performancing redesign is underway, and as I’ve been telling the team, it’s not only the redesign that will take much time and thought, but rather also the big move from Drupal to WordPress. I’ve been doing research on how this can be done. Unlike most other blogging platforms, the migration would not be a simple export-import operation, but rather, it would require some playing around with the database.
Sure, that can be learned and there’s nothing that cannot be accomplished with a bit of trial and error (of course, not on the live Performancing.com installation). But then I would like things to be as painless as possible, so if you have done a Drupal-to-WordPress migration yourself, I’d love to hear from you.
Also, one big question I’m facing is what to do with the existing content. For one, Performancing.com curently hosts thousands of blog posts and forum discussions, and this includes member-written blog posts. The team has decided to focus on importing into WordPress only the content written by the core Performancing editors and team members (past and present). The blog posts written by the community members would then have to be moved elsewhere. This is to make sure we don’t have an unwieldy amount of articles, which would definitely be against our intent of making the site more manageable.
Even then, this would require some discretion on our part. Firstly, importing articles would mean we have to preserve permalink structures (including paths) of these posts. Or would we rather just start fresh? One thing we could do is just keep just the more popular or the feature articles in their original path/permalink structures, and keep all the others under an archive. This might mean broken links and missing articles, which would be a pain for users who come across Performancing from the search engines.
Again, there are tradeoffs in this case. My question is whether we are willing to sacrifice some traffic for a faster, leaner site. And to what extent?
I think it will all boil down to user expectations. On the team’s part, the reason we’re doing a reboot is because we think Perf is due for some shakeups. We need fresh perspectives. We need something new. It ain’t broken, per se, and that’s why we’re breaking it, so to speak.
And so on your part, how do you think we can best handle the big move?