https://yawpitchroll.com/posts/hugo-probably-is-not-for-you/
After initial setup, the idea is you can edit a blog on any machine (not requiring Hugo locally). Just check out a repository, make changes and do a `git push`. All the hard work is done in a Github runner.
I wanted a simple way to be able to cut and paste screenshots into Markdown and generate a static site. Obsidian is both an excellent note taking tool and editor, so it seemed appropriate. Of course the markdown files can be edited with any editor.
[1] https://github.com/marketplace/actions/obsidian-to-hugo-page...
[3] https://blog.x1sec.com/posts/obsidian-to-hugo-github-pages-a...
It's not python, but it is a single binary to be off and running.
edit: Forgot to mention: The install option seems to be broken, you have to go into "Reference" to the install guide to find an alternative.
Add theme, follow tutorial, somehow blows up, need to figure out exactly where to put what, round and round then find a tiny wedge that works and just expand that until I have something that does what I need. But once it's set up it's really fast and you can iterate on your pages very nicely. No "tons of imports" that I needed with Jekyll.
Even as a dummy Product Manager, I've been able to write two plugins[0] for it over the last couple weeks (I'm one of the many laid off folks with a wee bit of extra time), and it's been a joy. Definitely frustrating moments — the docs could be better — but the maintainers have been super kind and helpful. It'd definitely benefit from a larger, more active community. Join us!
[0] Shameless plug: just last night, I wrote about one of those plugins here: https://ft.io/blog/link-preview-images/
The docs aren't great either but didn't find them as cryptic as Hugo docs.
Hugo has opinions on where files should be, how it should be transformed into pages. How those pages should be organized (ie: Taxonomies), and how users and template writers should be able to customize these elements to generate very different web pages.
------------
I do wonder if "Document Hugo" is the wrong approach, but instead the proper thing that needs to happen is "Create Beginner-Hugo-Template" and document that instead.
Then, "Create Intemediate-Hugo-Template" and document how various things you add to these Templates can improve a blog, or book, or various different webpage "ideas".
My favorite was Hexo: Reasonably simple, default setup looked good. I wrote a larger (but still mini) review of Hexo, gostatic, and Zola: https://linsomniac.gitlab.io/post/2023-02-26-simple_static_s...
Years ago I rewrote our entire company website, including hundreds of blog posts an articles, as well as marketing stuff, in Pelican in a day or two.
When I set up my Hugo site originally, I think I spent some time munging around and eventually got it to work, but that was years ago and everything I learned is lost. So I need something dead simple. But not, unfortunately, so minimal as gostatic.
[0]: https://www.sphinx-doc.org [1]: https://myst-parser.readthedocs.io [2]: https://myst-nb.readthedocs.io [3]: https://ablog.readthedocs.io