Replies: 1 comment
-
I also prefer our ToC. It might make sense to drop the ToCs if/when we'll be doing considerable changes to the structure of the files, to avoid having to worry about recreating/updating them (I often forget...). I don't think we should drop them proactively, though. In any case, thanks for pointing out the cool feature, as it's useful for other READMEs on GitHub that don't have their own ToC! (Also, I fixed a tiny typo directly on |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
GitHub now provides table of contents for Markdown files automatically!
This makes the table of contents in the README and the CONTRIBUTING guide less relevant. Should we remove them?
It's nice having the table of contents directly visible, and GitHub's TOC is not as readable and scannable as ours, so not sure. Just thought I'd point out this new feature. 😊
Beta Was this translation helpful? Give feedback.
All reactions