Cognitive aspects of navigation in gemini space

[solderpunk]

On Thu, May 14, 2020 at 09:40:49PM +0200, Katarina Eriksson wrote:
> Brian Evans <b__m__e at mailfence.com> wrote:
> 
> > I propose, also very hesitantly, that the following be optional elements
> > to code fences:
> > - The opening fence can be followed by a flag value of text or art (or
> > some other words that get decided upon, maybe even a or t)
> > - The closing fence can be followed by alt text
> 
> I was planning to suggest this when the spec freeze ends in a few weeks.
> Not sure if it's a good idea to put it in the spec or as a recommended
> convention.

There's an existing convention in Markdown, if I'm not mistaken, of
mentioning a programming language's name in curly brackets after an
opening code fence, which is used as a hint for syntax highlighting.
I'm not clear on the details, entirely, but people have mentioned it
before.

It might be smart to adopt/extend that syntax?

For now I am leaning toward "recommended convention"...

Cheers,
Solderpunk