web/MigrationFeaturesNeeded written at 02:31:20; Add Comment
What you need for migrating web content
In light of the wiki trap and the question of how to manage content, let's start with a basic question: suppose that you want to migrate from one way of storing and managing web content to another (such as in to or out of a wiki). What things do you need from your current content system?
Based on our experiences here, my answer is that the minimum you need is:
With HTML for your content, information about what URLs you need to either recreate or redirect, and the important metadata you can rebuild a basic version of your web area in either another system or with plain HTML pages. How much you need metadata depends on how much use you make of it. A support web area may not really care about things like authorship and publication date while a blog cares a lot, especially once you get to comments.
(I've reluctantly concluded that exporting any edit history is not usually important enough to be included in the minimum list. It's nice to have but in general not having it is not going to break your site, because usually the current page contents are the important stuff.)
The immediate corollary is that if you are picking a system to hold your web content and you care about not getting caught in the wiki trap, you want to make sure that your chosen system can give you all three of these things. Having these things won't make conversion painless, but it makes it much more feasible.
(In practice the question is never whether or not conversion is possible; it's always possible if you work hard enough, because in the limit case you manually crawl your website, copy the HTML of your content, de-mangle it, and so on. The real question is whether a conversion is easy enough to actually be done.)
* * *
Atom feeds are available; see the bottom of most pages.