As a happy user of Pelican[0], a different Python based static site generator. Why would I want to switch over to Ivy?
As a happy user of Pelican[0], a different Python based static site generator. Why would I want to switch over to Ivy?
I'm giving it a go this weekend, let you know if it worked out for me.
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).
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.