Mr. DrogDrog

fixed it. (to make things a bit easier for me I rebased this branch on https://github.com/ForkAwesome/Fork-Awesome/pull/354)

I removed the badges, because when I wrote this fork, I didn't think about creating a PR. I can add them again. That's no problem. I can fix the unit...

I didn't expect this PR to be merged in one piece because it's affecting to many parts of the code. It's more of an idea, what it can look like....

We don't generate the TOC ourself. We use https://github.com/nagaozen/markdown-it-toc-done-right for that. So if you want that feature you should open an issue there.

There is no frontmatter option for that in hedgedoc yet. We can add it, but it will take some time and it won't come to HedgeDoc 1. As you can...

Well. This repository contains the in-development frontend of HedgeDoc 2. So if you want this feature and can wait a bit, we can add it to HedgeDoc 2 :yum:

> Through one field each in the FrontMatter, We can do that and probably will. > or in the TOC tag its self: [TOC:1:3]. The parsing of the `[TOC]` tag...

Hello, > The timeline states the release for HedgeDoc 2.0 for 2021, which is almost over. That's only a tentative release date. Thanks for the hint. We'll change that to...

Fixed the changelog in https://github.com/hedgedoc/react-client/pull/1769

We could create a zip file (in frontend or backend)