When posting to a weblog I assume that you can only post one note and that there is no method, within Tinderbox, to assemble notes into one posting - as you would with an html page using templates.

Is my understanding correct or is there some method of assembling notes for 'direct' posting?

Thanks
RB

A further note: if you're going to assemble a post from many notes, and you're also working with attributes for tags and the like, you might ask yourself whether you're getting much (or anything) from using a weblog engine rather than simply exporting the site straight from Tinderbox.

http://HTLit.com, for example, is a weblog-like site that's made in Tinderbox.

Quote:


Hi Mark:

Thanks for the thought

Your site http://htlit.com/ is the similar to the type of configuration that I'm trying to build.
I decided on using a CMS (Expression Engine) so that I could reuse content as required.

Currently I'm working on using Tinderbox for two purposes:

• Provide a model of the site so that I've a map of how everything fits together.
• Act as the writing tool for producing new content.

In the existing paradigm I'm trying to understand how efficiently I can move content from Tinderbox to Expression Engine .

However, you make a good point that it might be possible to create the whole site in Tinderbox. I'll give that some more thought. (Note: I originally dismissed the idea of only using Tinderbox as my concept seemed too complex to implement in Tinderbox, which is say that I don't know that my programing skills are up to the job. Using a CMS and its tagging system seems to reduce the risk of continuing technical problems caused by poor programing.)

Can you point me to any existing tutorial/educational/help information regarding using Tinderbox as a CMS?

Thanks.

For those tempted to try, HTMLExportCommand allows you to apply a program or script to each exported HTML file. If HTMLExportCommand is empty, no special action is performed.

Otherwise, the exported file is piped to the standard input of the command line in HTMLExportCommand, and the file is replaced by command line's standard output. In other words, any action carried out by the linked command is carried out on the exported page after the normal page export.

Thus, if your command used curl to upload stdin (i.e. the output from the export template) the result would be a file on your server - or content in your CMS - rather than a file on your hard drive.

Hmm, brain failure, I should have written "...unix command line or shell script...".