4 ms·

Not sure if OP is the developer behind this but... As a happy user of Pelican[0], a different Python based static site generator. Why would I want to switch ov

Not sure if OP is the developer behind this but... As a happy user of Pelican[0], a different Python based static site generator. Why would I want to switch over to Ivy? [0] https://blog.getpelican.com/ https://blog.getpelican.com/

nicolaslem 9y ago
Pelican is great, I find it very flexible thanks to its many plugins. I wished it was maintained a bit more though, there are a lot of PRs waiting for reviews[0]. [0] https://github.com/getpelican/pelican-plugins https://github.com/getpelican/pelican-plugins
- hdra 9y ago
  That is just the plugins repository. I think a wiki model would work better for that kind of listing.
mixmastamyk 9y ago
I didn’t care for how it pushes a web server and absolute urls on you. Seems it could still learn a lot from Sphinx. As the sibling comment mentions I sent a pull request to fix some broken css and they requested I fix their test suite first. No thanks, moving on.
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 ago
  bookmarking this thread, as a pelican user I'd love to come back and read your experience on it vs Ivy
  - guitarbill 9y ago
    I 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).

nicolaslem 9y ago

Pelican is great, I find it very flexible thanks to its many plugins. I wished it was maintained a bit more though, there are a lot of PRs waiting for reviews[0]. [0] https://github.com/getpelican/pelican-plugins https://github.com/getpelican/pelican-plugins

hdra 9y ago
That is just the plugins repository. I think a wiki model would work better for that kind of listing.

mixmastamyk 9y ago

I didn’t care for how it pushes a web server and absolute urls on you. Seems it could still learn a lot from Sphinx. As the sibling comment mentions I sent a pull request to fix some broken css and they requested I fix their test suite first. No thanks, moving on.

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 ago
bookmarking this thread, as a pelican user I'd love to come back and read your experience on it vs Ivy
- guitarbill 9y ago
  I 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).