For my own usecase, Sass and syntax highlighting built-in are the things I wanted - Hugo now has highlighting built-in too though - and all of that in a single binary. I don't want to mess with virtualenvs or JS packages.
Compared to Hugo (which is what I was using until then), it has:
- the mentioned Sass compilation
- a much better template engine (I'm a bit biased there since I also wrote it)
- assets colocations: keep images etc next to the post
I also find it much easier to use than Hugo but I wrote Gutenberg for my own usecase so this point would need external validation.
I wrote a bit about the motivation when I released the initial version on my blog: https://vincent.is/announcing-gutenberg/ but I agree it should be better communicated on the landing page.
Rust is an implementation detail: it could have been done in any language compiling to a binary, I just picked the one I prefer.
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.
I 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
FWIW 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.
