Sounds great with "everything is a page" change! That is something I'm used to from ProcessWire [1], and which works extremely well there, getting at a very very flexible system.
I have used Hugo for my latest site (http://pharmb.io) and have been pretty happy, as most things seem to be pretty straight-forward to implement. It actually resembles the feeling of working with ProcessWire quite a bit :)
Though, if there is one thing I would recommend Hugo developers, it is to have a closer look at ProcessWire, for ideas on how to create an extremely flexible, yet straight-forward, light-weight and easy-to-work with, easy to theme, etc, system. I actually feel I still lack a bit of the flexibility in ProcessWire when working in Hugo.
ProcessWire also has a really nice way of generating thumbnails, which could be useful to Hugo too (echo '<img src="' . $image->size(640,480)->url . '">';).
Anyways, eagerly following the developments. While I love the system design of ProcessWire, I'm happy to see that something similar is shaping up in Golang, for increased performance and robustness!
I have used Hugo for my latest site (http://pharmb.io) and have been pretty happy, as most things seem to be pretty straight-forward to implement. It actually resembles the feeling of working with ProcessWire quite a bit :)
Though, if there is one thing I would recommend Hugo developers, it is to have a closer look at ProcessWire, for ideas on how to create an extremely flexible, yet straight-forward, light-weight and easy-to-work with, easy to theme, etc, system. I actually feel I still lack a bit of the flexibility in ProcessWire when working in Hugo.
ProcessWire also has a really nice way of generating thumbnails, which could be useful to Hugo too (echo '<img src="' . $image->size(640,480)->url . '">';).
Anyways, eagerly following the developments. While I love the system design of ProcessWire, I'm happy to see that something similar is shaping up in Golang, for increased performance and robustness!
[1] http://processwire.com