MUmunificent·Jun 5, 2018
For my blog [0], I use Jekyll. I'm not super enthusiastic about it, but it gets the job done. Ideally, I'd use a system that doesn't require as much futzing around with Bundler and pip (I use pygments for source highlighting, so Python is in the mix too) every time I touch it. It's kind of slow too.
For my first book [1], which is online too, I hand-rolled a tiny Python script [2] that converts the Markdown pages to HTML. It uses Python Markdown and that's about it. SASS for authoring CSS. (Weird observation: that 499-line Python script is probably the most profitable code I've ever written.)
For my second book [3], I took that script and gave it some more juice since book #2 has more complex needs around including code snippets [4]. It's still hand-rolled. In addition to Python Markdown, the other interesting library it uses is jinja2 fo
Read the rest
r templates. I like it.
I understand the arguments against rolling your own, but a blog generator is simple enough that the benefits of code reuse are relatively small. Meanwhile, the convenience of being able to jam little hacks specific to your need is very real [5].
When I get time to hack on my blog again, there's a good chance I'll ditch Jekyll and roll my own.
[0]: http://journal.stuffwithstuff.com/
[1]: http://gameprogrammingpatterns.com/
[2]: https://github.com/munificent/game-programming-patterns/blob...
[3]: http://www.craftinginterpreters.com/
[4]: https://github.com/munificent/craftinginterpreters/tree/mast...
[5]: https://github.com/munificent/craftinginterpreters/blob/mast...