Last night I started looking at what it will take to enable page-oriented editing of a Movable Type site from Radio’s outliner. Here’s a basic outline of the design:
1. The outline represents a full day’s worth of posts.
2. Each top-level item in the outline becomes one Movable Type post. [Alternatively, we could treat the entire outline as a single Movable Type post but this would make RSS feeds harder to generate.]
3. Items with no children in the outline are title-less. The item text is converted to HTML and shipped to Movable Type as the description.
4. For items having children in the outline, the top-level text is the title. Children are converted to HTML and shipped to Movable Type as the description.
5. Cross-posting is handled via the metaWeblog API. Plenty of sample code in Dave’s Getting started with Radio as a Movable Type Outliner.
6. We will try to be smart about not re-saving items that haven’t changed since the last save. We can do this by saving a copy to the local disk or database in addition to posting via metaWeblog.
I have begun coding this up and have a few questions, which I’ll post to the comments section.