Lusito

Markdown is a lot easier for non-developers to work with than HTML. It's also less dangerous. If you're not careful, someone might sneak in JavaScript into that HTML code. I...

>Also even Markdown needs to be passed through a DOM sanitisation tool or so as it can also include HTML. I use markdown-it for both the editor and my add-ons...

Not sure why this is such a problem, you can press the eye button in the toolbar and it goes away. Of course, it can be implemented, that the preview...

How would you solve these complex views like help pages if not by using markdown or similar? I don't see why markdown is a big no-no for extension developers.

If you use HTML, your translators need to understand HTML as well. It's a lot easier to teach people correct Markdown than correct HTML. Anyway, there will be options for...

Sadly, there is no way to submit a PR using just the website on github, at least as far as I know. So you'd have to ask translators to learn...

That view you are mentioning only exists for members of your project. Try that with my extension and you'll get an entirely different view: https://github.com/Lusito/forget-me-not/edit/master/_locales/de/messages.json

I'll look into it. If this was done, I would have to create a guide, since this will probably confuse users who know nothing of git. But I suppose it...

That sounds reasonable. I think credit should probably be managed in a separate file, since those names don't need to be translated and having to modify all translation files for...

I'm not sure if putting the e-mail of translators in the file is such a good idea. Having an entry "Translated into by " would be a nice thing and...