github-markdown-css VS texme

Nowadays, most application documentation is moved onto a website, which forces users to switch to a web browser every time they want to read some basic documentation. Furthermore, docs on the web can become quite convoluted, resulting in additional times spent just looking for the right section. But as it turns out, using the JavaFX WebView, Flexmark, AtlantaFX Popovers, and for example GitHub Markdown CSS, you can achieve a fancy markdown display within your application at exactly the place you want:

You can download a GitHub Markdown CSS and then I think use it as the Custom CSS in MarkdownPad.

sindresorhus/github-markdown-css - The minimal amount of CSS to replicate the GitHub Markdown style

github-markdown-css

I'd say if you can't find what you like just make something. I found this https://github.com/sindresorhus/github-markdown-css, maybe that can be a starting point? Good luck!

It probably won't cover needs of "make documents at our office" but I'd like to mention https://github.com/susam/texme. Basically you prepend your markdown file with a line of HTML/Javascript, rename it to HTML and it'll render pretty in a webbrowser.

This is nice. We are website-mates. My website is also 2001-2022. I like the simple and serif font on your website.

I had thrown in your https://github.com/susam/texme few times to quickly send Markdown files for reading. :-)

By default vs code has latex on md. Also https://github.com/susam/texme

So the Markdown to HTML rendering happens as page load time.

This would hopefully allow me to forego the static .md -> .html step I use for building my sites.

I found one called 'texme' here: https://github.com/susam/texme

Do you use or have written a similar tool?

Does the Self-Hosting heading not answer that objection?

https://github.com/susam/texme#self-hosting-texme

> Open source maintainers abandoning projects due to lack of time and interest.

And the occasional demanding users who would rather have us working on their problems instead of our own.

Only about a couple of hours ago, I received an issue[1] on one of my projects suggesting I fix an issue which from my perspective appeared to be a lack of understanding of the documentation I have provided with the project. Unclear issue details and demanding behaviour can take a toll on a maintainer's morale.

[1] https://github.com/susam/texme/issues/21