3 ms·
Not OP, but I'm tempted to switch. Because I had an issue with Pelican where I couldn't get year/month archives to work sanely (Pelican does year/month/day whic
by guitarbill 9y ago
Not OP, but I'm tempted to switch. Because I had an issue with Pelican where I couldn't get year/month archives to work sanely (Pelican does year/month/day which is too fine for me). So I had to write my own generator anyway, and plumb that into Pelican. It wasn't that easy to do, although I do think Pelican is fairly hackable, if anything else was more easily hackable/extensible, I'd use it. Plus not having Python 2 legacy stuff in the codebase is a plus when I'm grokking it. I also find the Pelican config overburdened [0], but understand why it came to be that way.
I'm giving it a go this weekend, let you know if it worked out for me.
[0] http://docs.getpelican.com/en/stable/settings.html http://docs.getpelican.com/en/stable/settings.html
- xref 9y agobookmarking this thread, as a pelican user I'd love to come back and read your experience on it vs Ivy
- guitarbill 9y agoI didn't get very far, because I found it hard to even specify which template a page should use. I tried to do it via the YAML front matter, but that gets clobbered. I could have written an extension that un-clobbers/sets it via the 'page_templates' hook, but there are other problems. You'd have to re-write all your links, and the way you attach e.g. images to a post (for me the biggest deal breaker). You'd also have to write your own extensions for tags, neighbour pages, and much more. To be fair, the author never claimed it replaced Pelican or any other blog-capable static site generator. If you have a very simple site, it could work. I also get the feeling Ivy is a bit of a vehicle to push the author's replacements for argparse (janus), markdown (monk), and jinja (ibis).