1. 15
  1. 5

    I did this once upon a time, except I created my own in Racket instead of using Pollen. It was a fun exercise, but it got very complex and hard to follow with my poor code design. I might try going back and using Pollen soon.

    The fun part was indeed using Racket to use it’s batteries-included library to publish things like graphs. If you use limited minutes on a CI service like GitLab CI/CD, Racket is a massive time hog as it’s Docker image is quite large, and since it’s not the fastest language around. But other than that, Racket is pleasant to use and easy to customize in many ways.

    1. 3

      I also have built my blog with pollen and really enjoyed the process of doing so. One issue I frequently ran into is debugging while developing a new feature, that experience is not yet fine-tuned for a developer, especially one that doesn’t have extensive experience in racket. But asking in the forum can be very helpful and did help me in more than one case.

      In general I don’t like the pollen server since it doesn’t include anything for live-reloading, which I find very important. As such, I went a completely different route and now use redo together with watchexec and a Firefox plugin for reloading. Specifying the dependencies is a bit awkward since racket does not work well with calling redo from racket and as such my build tool is currently a hodgepodge of shell and racket scripts, but it works on my machine.™

      All in all, the idea of using sexprs for representing a blog post is simply beautiful and I wouldn’t want to miss it anymore.