- Colorado
- https://git.sr.ht/~nytpu/
-
does code and sometimes even other things. ~nytpu on tilde.team. i've mostly migrated to sourcehut: https://git.sr.ht/~nytpu/
- Joined on
2020-05-19
I think for shorter stuff either style (end of section or end of any header block) works, but we should probably keep it consistent, maybe say that if you have <2–3 links in each subsection and the section is short enough move it to the end of the section instead, but it's your call on whether you want to have two separate options for people or not.
I agree on the persistent link numbering, there's no harm in doing it even if the browser doesn't number links, and it makes it easier if you want to search for a specific link you could search for "[3]" to find just that one link.
A few other things to decide on are:
- should the footnote numbers be persistent throughout the whole document or "reset" after every section/subsection?
- should the text for the link be aligned (this is more the writer's preference over the consumer's preference but still)
example:
=> gemini://gemini.circumlunar.space/capcom/ [1]: capcom geminispace aggregator
=> gemini://gus.guru [2]: gemini univeral search
Just a minor thing, but I think that links should be placed at the end of the content but before the next header.
Example:
# title
hello[1], world!
=> https://en.wiktionary.org/wiki/hello [1]: definition of hello
## section
good morning america[1]
=> gemini://vault.transjovian.org:1965/text/en/Good%20Morning%20America [1]: gemini wikipedia — good morning america
### subsection
infinite content[1]
=> gemini://vault.transjovian.org:1965/full/en/Everything%20Now [1]: the album everything now has a song called "infinite content"
It just doesn't look as good like this, especially if you imagine multiple long (i.e. taller than the display viewport) subsections:
# title
hello[1], world!
=> https://en.wiktionary.org/wiki/hello [1]: definition of hello
## section
good morning america[1]
### subsection
infinite content[2]
=> gemini://vault.transjovian.org:1965/text/en/Good%20Morning%20America [1]: gemini wikipedia — good morning america
=> gemini://vault.transjovian.org:1965/full/en/Everything%20Now [2]: the album everything now has a song called "infinite content"
yeah, I think a md-to-gemini tool would be trivial, the only difficult thing would be parsing and organizing the links. I was thinking a gemini-to-md tool would be easier to write since gemini is so easy to parse compared to markdown, but we'd have to rewrite our existing documents in gemini.