@satikusala, it has indeed. I will write you so we can catch up.
The idea of using the IDs occurred to me as well, but since this is for a documentation-styled site, I would still need to use the path to create human-readable slugs, after all,
site.io/bibliography/bibtex seems more readable than
site.io/1653940245/1653940255 (not that I would mind too much having the second, but I think the first option is the norm).
@mwra, I am using a form of redirection to allow sub-notes to be linked. A note exported as part of another note (a child note) will also be exported independently (but empty and un-listed) to allow link-to-section. The links to the empty notes get edited so that they will link to
collect_if(ancestors(this), $Prototype=="Post", $HTMLExportPath) +
# + the note name (that is also the section id in the full post). I think It would be tricky to achieve this using relative links.
Moreover, the mkdocs documentation states that all links need be relative to the root folder
/docs/. Tbx links need to be edited if I am not to change the root folder of the site (Tbx adds a forward slash in links so this would create
I think that if Tinderbox could support a system/local attribute to allow all links to be exported relatively to a single base path, it would be helpful and this would go a long way toward turning Tinderbox into a useful tool for writing documentation using static-page generators. Could this be considered, @eastgate?
(To be clear: I managed to get it working properly, so no real change is really necessary for this to work. But it seems like it would be a sensible addition.)