I've started a project to create a WordPress to BlogML converter. It's somewhat self-serving, as I have several blogs I'm interested in converting, and couldn't find a good solution available. While BE.net wouldn't be the only customer of the
output from this project, I know that this user group is knowledgeable about what would be good from a user standpoint.
So, the first thing I need to decide is which end to target. Currently, I'm kicking around two options. They are below; please reply and let me know which you think would be more valuable.
Option 1 - Create a plug-in or theme for WordPress that will utilize WordPress to send the output to either the browser or the filesystem.
Pros: Most(?) WP bloggers know how to install a plug-in. It's a non-geek solution.
Cons: Would be written in PHP. On larger blogs, it could run into problems with resource limits (memory/execution time) that cannot be overridden on shared hosting plans.
Option 2 - Create a process that reads the MySQL database backend of WordPress directly.
Pros: Eliminates possible WP interference between data and output. Would be written in C# (which could be extended to automatically import into BE.net and other destinations).
Cons: Requires database access - for shared hosts, this wouldn't work unless the user did a backup-and-restore to their local machine (a much more "geeky" solution). If a user is going from shared-Linux to shared-Windows hosting, this
may not be as easy as option 1.
Of course, both options are subject to WordPress changes; that's a given. Option 2 would only be subject to database changes, while Option 1 would also be subject to internal representation within WP's PHP code. Personally, I'd prefer option
2; I think that somebody that knows enough to want to do this migration would probably have a level of knowledge such that getting a backup wouldn't present a challenge.
What do you think? Let me know!