Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ivy – A static website generator built in Python

mulholland.xyz

Post reply on HN
Print view View original

71–76 of 76 posts

Re: Ivy – A static website generator built in Python

#71

Post by hdra »

nicolaslem wrote: post #9
jaredandrews wrote: post #6

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/

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

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

Re: Ivy – A static website generator built in Python

#72

Post by Drdrdrq »

zmmmmm wrote: post #68

General question - I don't understand why so many static site generates, github, many others, all use templates that won't fill the width of the page. Is using the full width of the page particularly difficult to design for? Or is it an aesthetic decision that template authors feel like having a 20 inch wide monitor with 8 inches of text in the middle flanked by 12 inches of white space is a nice layout? Particularly…

Depends on width of the monitor, of course, but one reason would that it is easier for reader to follow lines if they are not too wide. The same reason is behind multicolumn layout in newspapers.

Re: Ivy – A static website generator built in Python

#75

Post by guitarbill »

xref wrote: post #65
guitarbill wrote: post #63

Earlier quoted context omitted.

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…

bookmarking this thread, as a pelican user I'd love to come back and read your experience on it vs Ivy

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).

Re: Ivy – A static website generator built in Python

#76

Post by pleasecalllater »

zmmmmm wrote: post #68

General question - I don't understand why so many static site generates, github, many others, all use templates that won't fill the width of the page. Is using the full width of the page particularly difficult to design for? Or is it an aesthetic decision that template authors feel like having a 20 inch wide monitor with 8 inches of text in the middle flanked by 12 inches of white space is a nice layout? Particularly…

The best length for fast reading is not more than 60-70 characters per line. That's why you have columns in newspapers. I have a 4k 26 inch monitor. Full width texts are harder to read, I have to shrink my browser to make the text not so wide.
Post reply on HN