21–30 of 39 posts
Earlier quoted context omitted.
It doesn't have footnotes. Some supersets do.
Right, but it's worth noting that those supersets are very common. I'd say it's actually less common to run into a "barebones" Markdown implementation these days than to run into a GFM or close-to-GFM one.
Breck, you're a good programmer, just like Terry A Davis!
- Sent from TempleOS
Here's the same sample as OP in Markdown Footnotes syntax. There is a link to the rendered page [2].
https://gist.githubusercontent.com/richsuca/f5a14ed9cb76e7ad...
[1] https://python-markdown.github.io/extensions/footnotes/ [2] https://gist.github.com/richsuca/f5a14ed9cb76e7ad2f4f6b11361...
My favorite way is how French website "Le Monde Diplomatique" does it : the footnotes appear at the bottom of the screen in context as you scroll so that only those referred in the currently visible text are displayed. It avoids awkwardly clicking on tiny superscript numbers and annoyingly scrolling back and forth between text and footnotes. For an example : https://www.monde-diplomatique.fr/2021/01/PIGEAUD/62633
My favorite way is how French website "Le Monde Diplomatique" does it : the footnotes appear at the bottom of the screen in context as you scroll so that only those referred in the currently visible text are displayed. It avoids awkwardly clicking on tiny superscript numbers and annoyingly scrolling back and forth between text and footnotes. For an example : https://www.monde-diplomatique.fr/2021/01/PIGEAUD/62633
this is beautiful implementation. Would be nice to see how implementation was done ?
Anyone interested in footnotes might like the way we do it on the Vale site, for example: https://verdagon.dev/blog/making-regions-part-1-human-factor Some nice things: * The footnotes are off to the side, so it's closer to the text that mentions it and it doesn't interrupt the flow of the main text. * It uses colors, so it's pretty fast to visually jump to the right one. * We keep the numbers too, for colorblind fol…
You may want to explore Tufte CSS. My own article about footnotes/sidenotes: https://ab1908.github.io/2021/08/24/footnotes-in-web-content...
Anyone interested in footnotes might like the way we do it on the Vale site, for example: https://verdagon.dev/blog/making-regions-part-1-human-factor Some nice things: * The footnotes are off to the side, so it's closer to the text that mentions it and it doesn't interrupt the flow of the main text. * It uses colors, so it's pretty fast to visually jump to the right one. * We keep the numbers too, for colorblind fol…
I think the colors idea is good too. Some stuff for us to play with in the future.
Thanks for sharing!
Anyone interested in footnotes might like the way we do it on the Vale site, for example: https://verdagon.dev/blog/making-regions-part-1-human-factor Some nice things: * The footnotes are off to the side, so it's closer to the text that mentions it and it doesn't interrupt the flow of the main text. * It uses colors, so it's pretty fast to visually jump to the right one. * We keep the numbers too, for colorblind fol…
You may want to explore Tufte CSS. My own article about footnotes/sidenotes: https://ab1908.github.io/2021/08/24/footnotes-in-web-content...
At the risk of Dropboxing myself: what is the advantage of this over the existing Markdown syntax for footnotes[1]? It looks very similar, but with a harder to parse grammar. [1]: https://www.markdownguide.org/extended-syntax/
This made me laugh. I appreciate you.
> but with a harder to parse grammar
Grammar is actually quite simple once you've mastered the Grammar language (https://pldb.com/languages/grammar.html) which has almost no documentation and is full of bugs.
> what is the advantage of this over the existing Markdown syntax for footnotes[1]
I can't speak definitively yet. I think it will be better but I need to use it for a few months to be sure. There are some subtle things I think will be important.