2 ms·
This is cool, and props for scratching your own itch, but this does seem like an incremental/niche improvement over Hugo. I'm curious if you talked to the Hugo
by weberc2 9y ago
This is cool, and props for scratching your own itch, but this does seem like an incremental/niche improvement over Hugo. I'm curious if you talked to the Hugo community about supporting those features? I don't mean to imply that you should have done so--"I wanted to build my own" is a totally valid reason not to bother.
- Keats 9y agoI don't really like the template engine available in Go (especially the godawful one in the std) so I would have needed to write one or use pongo2 but probably wouldn't have been accepted in Hugo: https://github.com/gohugoio/hugo/issues/1359 https://github.com/gohugoio/hugo/issues/1359 The assets colocations issue was raised in 2014 and it might come soon but I don't think it's there yet: https://discourse.gohugo.io/t/keep-images-content-together/51 https://discourse.gohugo.io/t/keep-images-content-together/5.... Same thing for Sass compilation: https://discourse.gohugo.io/t/support-for-html-css-js-preprocessors/127 https://discourse.gohugo.io/t/support-for-html-css-js-prepro...
- scrollaway 9y agoFWIW I'm glad you wrote this. Having looked at Jekyll alternatives before, the field is severely lacking especially in terms of static sites generators that don't immediately assume you're publishing a blog.
- weberc2 9y agoCool! Thanks for the information. Good luck with Gutenberg!