This looks decent, though I'm thinking we should keep the Table of Contents.

That seems like it's probably useful because we have lots of sections. 😄

This looks decent, though I'm thinking we should keep the Table of Contents.

That seems like it's probably useful because we have lots of sections. 😄

I think @lucydodo is removing it because you can display a TOC from the menu button. But I think that many people don't know that and will probably miss it. I knew that, but I always forget about it.

Ideally, GitHub should have a pragma to include an inline TOC in the markdown document, but I looked for it and found nothing.

Ideally, GitHub should have a pragma to include an inline TOC ...

Oh. That reminds me... Asciidoc (rather than Markdown) has that capability.

For example, when the "WebAssembly" wiki page on the Go wiki became pretty long, I converted it from Markdown to Asciidoc specifically so it could autogenerate the ToC.

The first few lines of that file (in raw text mode) are now:

WebAssembly
===========
:toc:
:toc-title:
:toclevels: 2
:icons:

Which generates the Table of Contents seen here: https://github.com/golang/go/wiki/WebAssembly

That being said, I'm not really a fan of Asciidoc otherwise. Markdown seems more natural (to me), though that's probably just a familiarity thing.

Correct. I removed the TOC because, as @mgrojo said, GitHub added that feature.
To be honest, I often forget about that feature too (I don't think it's very accessible).

I don't mind adding it back because it doesn't make it less readable and it's not that hard, what do you think?

I reckon we should add it back. That way it works for everyone that reads the page, and people don't have to know about special GitHub buttons. 😄

Added a TOC. Any thoughts on the postion of TOC?

Table of Contents placement looks good, and everything else seems fine too.

Happy to merge this, unless there's other stuff that needs doing to it? 😄

Sure, Go ahead! :)

Done. 😄