Hi, new hugo user perspective here.
I found that it is nearly impossible to build a very simple static site with a few top level pages that could still be edited by a non-tec user. just imagine a very simple site like this:
NO folders, no subdiretories (in content) nothing else, very simple. Of course the user should be able to edit the index.html frontpage and add another page if she likes and the menu should be generated automatically.
This is nearly impossiible to build with Hugo because of limiting assumptions. OK, maybe not impossible, but I did not find a clean way to build a result that still will be understandable for end users.
Instead I have to use hacky config elements - e.g. uglyURLs = true - why this option has even remotely anything to do with the fact that subfolders are used or not is not understandable. Also at some point I had a “.html” file in the public folder generated, I do not clearly remember what caused this - I then found after a few hours the github issue with the workaround for editing index.html. OK, and now create a menu - of course the menu from the documentation did not work, well, maybe because I did not follow hugo assumptions and just putting five md files in content breaks eveything, sigh.
I stopped there and did not even look into how to integrate gulp or webpack - what of course should be integrated out of the box in any way, not left to the user as another workload.
Please understand me - I am not ranting (ok, a liitle bit maybe), I am trying to make you understand that you are creating a much too limiting set of assumptions with this piece of software and it leads to the situation that the most simple default usecase does not work.
Please while developing new versions of your node concept always try to also test for the simplest and most easiest use case: a user that just creates max. ten top level pages in /content - no directories, sections, types or whatever. SOme images and a little bit of css and js in ONE top level folder like e.g. “assets” - and of course an autogenerated menu from this. Very simple, too simple for Hugo as it is now. But this is the “default” use case for thousands of mini-personal-websites that do not need wordpress for that - and still this is too complicated with Hugo. The features that are already there are very nice to have, but to build the simplest sites it gets too complicated for most of users out there.
It would be great if Hugo made zero assumptions about how to organize content, but still allow the strong organizational features for advanced usage.
Thanks for your attention!