You’re welcome!
And, you are absolutely right. I did gloss over that detail. I always put the target reference in a top level header at the beginning of the document. Generally I create a stylesheet with:
body h1:first-child { display: none; }As a rule which hides this first header from display in a browser. You don’t need brackets in the name. The use of a simple [bracketLink] in MMD is just a shorthand method for [bracketLink][]. They both do the same thing. The idea is, if you are not going to be needing to alias the link with another phrase, you might as well reduce complexity.
So [ic07193687] will create a link to a spot in the merged file that corresponds with:
# ic07193687 #Even if the stylesheet is currently hiding the visible component from display, it will still work.
I put the two letter identification bit in front because the XHMLT spec requires a non-numerical character in the first position of an id. Otherwise, I’d just use the number. I suppose I could just use a generic two letter thing like, ‘id07193687’, but I figured why not indicate if the linked item is going to be a short paragraph or two, or an entire article.
Another alternative, if one wanted to create a network of thoughts instead of merged pages, would be to create a link to where the other file would be. If they are all going into the same web directory, [Index Card on Bamboo Fibers][./07194756-R-BambooFibers.html] would do the trick. In that case, you wouldn’t need to create a target link in the destination file at all.