Right now I set up this weblog to be rendered on my laptop and upstreamed to the server with normal HTML pages. This somehow put the burden of organizing the site on Tinderbox. But somehow I get interested in the idea to let the server care for the public face of my content and rather use Tinderbox in a “freestyle” way. The server should only get a “content feed” from which it should construct a site.
One rather simple way would be to publish the Tinderbox content directly into a database on the server. The quickest (and dirtiest) way to do that would be to render SQL files and use a script on the server to import these. The HTML rendering would be completely the job of the server (and of course I’d need to set up templates & everything there).
A more sophisticated approach would be to render XML files that are parsed into the database. This would maybe allow to reduce the amount that needs to be uploaded per update.
Unfortunately I don’t think I am going to have the time to check this out. But somehow I hear a distant voice telling me that this would even allow several Tinderbox users to work on one site together (or at least publish into the same space).