Ah - sorry, that didn’t come across from your opening post.
OK, if I now understand correctly, you want to include in the exported HTML page some/all of a note’s KeyAttributes? Did you look at the aTbRef templates? Consider how this page is generated:
So the ‘KA table’ part is added by ‘including’ content for the current note using a different template ‘5-basic_item_attribute’. I won’t post all the code for the latter here, but you can look it up in the aTbRef TBX doc. You will note that the table items, i.e. the number of ‘KA’ rows is hard-coded. At the time I wrote it it would not have been possible to live parse a note’s $KeyAttribute values but I suspect it could be done - albeit in fairly byzantine fashion - using ^action()^ calls to wrap list.each() loops. Both the latter’s usage is described in aTbRef.
If the included values need to be in the ‘body’ of the text, then you have no choice but to put the export code, e.g. ^value($SomeAttribute)^ into the the source $Text. So you will see the export code when looking at the note in the app.
Anyway, give the above a try, and ask here if stuck.
I’ve made a note to extend my export demo to better cover this aspect - although the more complex the export the harder it is to generalise for the new (export) user. 