|
|
|
|
|
|
by dancek
1963 days ago
|
|
|
IMHO you could just use # Page title
# 1. First heading
and go from there. The format is meant to be human-understandable, not machine-readable.But your point is a good one, and made me wonder how the documentation of Gemini itself handles the issue. And behold, the Gemini FAQ [0] itself has the first level 1 heading as ## 1. Overview
and the second one as # 2. Protocol design
That's really disturbing once you notice, but I'd wager that hundreds of people have read the page and not noticed.[0]: https://proxy.vulpes.one/gemini/gemini.circumlunar.space/doc... |
|
|
I disagree that it's not meant to be machine-readable. Accessibility clients rely on heading levels to infer sections and subsections. HTML has `<section>`, but a Gemini client only has heading levels to go by.
But anyway, that's why I said it'd be "awkward", not "impossible", to reuse the title heading level for section headings. The rich-text Gemini client as well as the human user reading the raw file have to special-case that the first `#` is the page title and not equivalent to other `#` in the file.
And like I said, even once you get over that awkwardness, three levels is still very limiting. I'm looking at a markdown documentation file right now that has five levels of headings. That's with one unique level for the page title, so even if it were to reuse the title heading level for the section headings it would still require four levels of headings.
>And behold, the Gemini FAQ [0] itself has [...]
Ha, I didn't know about that one. I had noticed in the past that the homepage [1] uses a unique level for the title, but the specs page [2] does not because it can't afford to.
[1]: https://portal.mozz.us/gemini/gemini.circumlunar.space/?raw=...
[2]: https://portal.mozz.us/gemini/gemini.circumlunar.space/docs/...