Sheogorath

I wrote a first draft for a guide, maybe needs some testing and validation: https://demo.hedgedoc.org/WDjvPVweTBWqVyUEg8A6Kw# Feel free to try it and give some feedback :)

It would however make sense to adjust this in the default CSS as part of the accessibility efforts for 2.0, if not already the case.

I just tested it on my private setup, which is also using keycloak + oauth. worked fine with both base images. Could you share your config?

I'll look into those details later and try to reproduce. But for now, please check the volume mount! This is not where uploads on the hedgedoc image are stored!

I once tried to build that, but it turned out to be a nontrivial problem. There are things like punctuation which should be ignored, as well as emoticons. And one...

I also don't know if it makes sense to have comments etc. Within the document or if it would make more sense to keep them outside of it. There is...

No, I highly advocate against merging this into the source code repository, because it'll cause more confusion, not less. If we integrate it we would copy souce code Form inside...

We should **not** merge with the main repository. It's all bonkers. It's breaking container image updates. We currently release a new container image version **every time the base images are...

Technically speaking they become inaccessible, not deleted, since on can revert to older digests. However, I would argue, if you need pinned version, please host a (pull through) mirror. I...

This is a quite layered issue: First of all, yes, it seems like something got lost when refactoring towards webpack 4. The subdomain in general. This feature should come back,...