btrem[KevinMarks]++ thanks for replying yesterday re: keeping track of footnote numbers. Sorry, I only just now saw your reply. I think a macro would have the same problem. Each macro call is independent. It wouldn't know that it had already been called on that template.
btrem[KevinMarks]: I can't imagine how. The problem as I see it as that every invocation of a shortcode or macro would be a new call to the js function. But I'm not a terribly advanced js programmer, so maybe I'm missing something.
btremI hate to rely on stylesheets for something that is core content. It's a clever idea, but I'm sort of trying to do the same thing with 11ty/front matter/static html.
ZegnatI liked it for the page I do it on, because it actually makes a partial sentence (multiple words) into the <a> that links to the explaining footnote. So the number is actually just an extra visual aspect to enhance the link
btremZegnat: I can see how that might work. Though it's an unconventional way to mark footnotes. In a sense, I was trying to replicate css counters in my 11ty shortcode. So each footnote ref would have been {% fn %}. And the footnotes would be an array of strings in front matter. The second part is easy, and done. The first part probably can't be done.
[KevinMarks] Can you do it with a nunjucks macro? That would let you keep state in a variable.
Zegnat Per this old article https://www.sitepoint.com/accessible-footnotes-css/
btrem Zegnat: I can see how that might work. Though it's an unconventional way to mark footnotes. In a sense, I was trying to replicate css counters in my 11ty shortcode. So each footnote ref would have been