I found this a bit confusing to follow as there are a number of misunderstandings here and you are perhaps overthinking the process. In a new document with notes you wish to export, just add the built-in ‘HTML page’ template (via the main File menu) and Tinderbox will _automatically add the necessary template(s) and prototype(s). If only one export template is present it is used as the default (HTML export) template for all notes - until and unless you add and set other template(s). Now use File → Export and all notes bar your Templates and Prototypes folders will be exported. That’s the default - you can configure the document to export fewer notes as there are controls (attribute settings) built into the app to allow export control down to per-note level. Assuming there is an HTML template in the document, Export selected note will export only the currently selected note.
The only purpose of the ‘HTML page’ prototype is to make sure template notes are best configured for adding export code - a good example is that the prototype suppresses auto-correction of straight quotes (which HTML browsers recognises) to ‘curly’ typographic quotes (which they don’t†). It also sets a monospace font so you can see whitespace accurately as this can be important in some export contexts. If unclear as to the role of prototypes see here and here.
† Web browser HTML code parsing is beyond Tinderbox’s control.
Also note that the prototype for export templates was renamed in v8.1.1. If added for the first time in a doc using v8.1.1+ the name of the prototype is now ‘HTML’. This change does not affect pre-existing documents with an existing ‘HTML Template’. Both do the same thing. The naming was changed because some users misinterpreted the prototype’s [sic] name as meaning it was a template rather than a configuration prototype for a template.
So, the number of items needed for export is just two and not three (as you have suggested). Thus:
- a source document (the thing you wish exported).
- an export template.
Even if you subsequently delete the template, adding the built in
If you haven’t already try this demo: TB7-HTML-export.dmg. Although written when v7 was the Tinderbox current version, the same processes hold true.
Tinderbox’s ‘HTML’ export is very powerful, but the app is a toolbox. You tell it which tools to use, rather than it only allowing you certain tasks (as might be true in other apps). The term ‘HTML’ is used as back in 2001, blogging & HTML page creation were seen as one of the likely uses of the app. The Web, or use of it, and text-based code have come a long way. aTbRef’s templates (in its source TBX) give an indication as to how quite powerful and nuanced export templates can be made.
Notwithstanding Preview mode in the text pane, this is not an app for WYSWYG HTML page design.
I strongly suggest working through the exercises in the DMG linked to above as it shows most of the basic processes and should help clarify some of your miss-assumptions‡ as to how export works in Tinderbox.
‡ That’s not meant in an offhand way. We all make assumptions when forced to guess, and sometimes these are incorrect.