well here is the brief concept:
it is a markup language for APP (NOT WEB) GUI’s, for Linux
but:
1: it does not have to depend on a single GUI Toolkit (GTK Or QT)
2: it depends on external Programs called “Translators” which translate the Markup language calls and whatever onto something your GUI Toolkit understands
3: it does not manage any form of functionality whatsoever, you have to depend on a another language to do that
what it aims to do:
sometimes a GTK app on a QT Desktop Environment
just does not match the theme
which that idea aims to solve
how would you fix it


Markdown was built to be easily translatable to HTML, so a simple web rendering engine like Servo is probably your best bet.
pandoccan be used to convert Markdown to HTML, for example.i may have to edit my post to clearly reflect it that it is for desktop apps not A Website
Oh no, I did understand, I just don’t think it’s worth reinventing the wheel in this regard. HTML is also just a way to instruct a UI renderer what to render. And for the simple stuff that Markdown allows, going through the HTML rendering pipeline is not much overhead.