Table of Contents#62

Option to enable generating the TOC by headings inside the content

This is possible manually using internal linking. Each heading has a unique ID that is the slugified title. It is possible to manage the ToC by creating a list of internal links at the top of the page.

https://herman.bearblog.dev/markdown-cheatsheet/#links

I understand that this isn’t the ideal solution, but it’s more flexible than a fully auto-generated system. Will still give this some thought though :)

Could you add an example for more complex titles¹ with spaces, umlauts and so on?

Or present a way to get the slugified title. (Might be the more universal solution.)

·-·-·-·-·-·-·-·-·-·-·-·-·-·

I would really like to use a floating, autogenerated ToC.

Especially for larger posts where it’s a navigation tool for the visitor to find their way in the “mass of content” that is present.

Possible settings include:

• Display to the right or left (could be top or bottom on mobile).
• Index depth (what header levels to include).
• Size.

–
¹ äöü ß µ @ æ …

I have jsut posted a very big blog post which would really use the help of having a ToC table ready at hand to navigate through !
See here: https://colin-crapahute.bearblog.dev/aztlan-postmortem/

It looks like this is supported by a “directive” plugin for Bear’s Markdown renderer.

I found that “Mistune” connection on an old “plugins implemented” post here on the Nolt board. If that’s changed, then this is meaningless. But — if it’s still true, then it seems as if implementing TOCs for posts would be relatively painless.

Using ChatGPT, I’ve generated a table of contents for colin’s blog:

Table of Contents: https://pastebin.com/1MWZAd3d
Blog post: https://colin-crapahute.bearblog.dev/aztlan-postmortem/

It may not be accurate, but ChatGPT is a great writing tool.