Re:Show HN: TeXMe – Self-Rendering Markdown and LaTeX Documents
by bhl on Friday October 26, 2018 @04:36PM
(#18312531)
Two different approaches: Jekyll is often top-down, start with a theme that you like and make edits to the css and html files until you get something you like. Downside is if you want to make major changes, you’ll have to understand complex code you didn’t write yourself. The approach given by this post is bottom-down; start with some basic css edits. Downside is you may spend enough time customizing that using a Jekyll would have been better. ️
Re:Show HN: TeXMe – Self-Rendering Markdown and LaTeX Documents
by SagelyGuru on Saturday October 27, 2018 @04:20AM
(#18314844)
That is true. I have used Jekyll but having to study obscure settings files and complex directory structures is not enjoyable when all you really want to do is to get on with writing your blog.
I know, the proper way is supposed to be to use Jekyll or Hugo or something like that, to compile to raw html on the server side but this is much simpler for the publisher. No configuration and compilation and updating on the server involved.
I do not think that the user will notice or begrudge the few milliseconds of processing in his browser. Especially if this could be converted to a WASM module. Any takers?