Blogs/CMS: somehow restore the Markdown

[SergioGlorias]

Markdown has been removed from Blogs and the CMS due to editor issues.
The Toast UI (editor) stopped being updated more than 3 years ago.
These bugs are reported on the publisher's GitHub, but they have never been fixed.

My idea is to change the editor to something more up-to-date and with a new look.

Why?

Some users (myself included) prefer the practicality that Markdown provides, and some features have been lost in favor of something more complicated to write.
Even drafts outside of Lichess have become more complicated to copy without having to make manual adjustments.

[yafred]

I agree.

I am a page editor but not the author. So, I just replace the content after comparing the markdown to the previous version.

I can't do that anymore.

[ornicar]

Good luck to the person handling that. Rich text editors are usually a massive PITA.

[SergioGlorias]

I found 1 list with editors
https://github.com/JefMari/awesome-wysiwyg-editors?tab=readme-ov-file#standalone
some have markdown others no

[Siderite]

What I feel would benefit Lichess as well as the users is somehow unifying the blog and forum mechanisms so that they become consistent and predictable. Also, one point of failure.

As for the editor itself, no idea what it should be, but I would suggest something that has enough hooks to can be customized via plugins or something added on top. This way one can update the editor and also maintain custom Lichess functionalities or bug fixes that the maintainers fail to implement.