jekyll-multiple-languages-plugin VS markdown-live-preview

Internationalization (i18n) pain for a documentation project is a process problem, not a feature gap. Documentation frameworks are not meant to translate your developer docs for you into the language of your choice. Some frameworks might offer i18n support, like the Crowdin support in Docusauraus v2. With Jekyll, you have to pick a theme like this one. I doubt if the reST or adoc frameworks would differ much from this process. Besides the framework support, you'll need a localization vendor like lokalise or a community driven platform like Crowdin to actually do the translation. Sébastien goes into great detail in this Docusaurus RFC when discussing i18n support in Docusaurus v2.

If you want to try out play with Markdown Language - click here: https://markdownlivepreview.com/

A while ago i make myself a list of possible ways to make a GUI (im not formatting it to reddit-specific markdown, sorry, paste the following text in https://markdownlivepreview.com/ or something if its not readable) :

You can use the "Markdown Live Preview" tool to look at the page format of any Markdown files.

dillinger or markdownlivepreview

If you're just starting out with Markdown, check out the syntax and write some hello-world docs online.

I'd recommend using a Reddit comment preview tool before posting. Like this one: https://markdownlivepreview.com/

Solved ! I just need to clone https://github.com/tanabe/markdown-live-preview and run script and voila, offline markdown editor and preview on qutebrowser.