Thanks BeccaPrice
re the buttons, my thought was to place them in a horizontal row at the top with no text - a'la the favourites button - which I was too scared to suggest - but just discovered
Its not important, now I know the buttons are there. I have a preference to have buttons, tabs, ribbons & bows at the top or down the sides of windows, reserving the bottom for status & error messages. I think it was Microsoft who started putting bars and buttons at the bottom of navigation panes - so we can blame them
By "when you've taken it as far as you intend' what I meant was when its out of the initial development phase and into maintenance phase.
Re glossary -
Metadata Jacket - what's the reason for them, why would I want, or not want them, and where would I get them - I know I can delete them in the Modify Plugin.
Its all very well to document Process, but if the reader doesn't understand the purpose of the Data that's being processed then ... A common characteristic of a lot of technical documentation, is the assumption that the reader has in depth domain knowledge.
Becca - that's not a criticism of you in particular, but of the information industry in general.
<rant>The 'trick' is, when one writes/reviews a sentence in a "how to document", ask oneself "would someone who knew diddlysquat about this knowledge domain know
the what, the where and the why of the object of that sentence". If not then define the object term in the Glossary, and put a reference to the definition in the sentence (hyperlink, whatever).
</rant>
BR