docs VS gutenberg

I can recommend https://linode.com, their documentation is excellent https://www.linode.com/docs/ and ready made images also https://www.linode.com/docs/marketplace/

>In other words, let the machine do your thinking for you No, this was idiotic. A generator tool like Hugo doesn't "think" for you. it's a tool, used by a thinking person. Even if someone new to HTML publishing happens to adopt Hugo, they are going to learn things. By the sounds of it, it's likely they will learn things you have not. They will still learn about HTML and CSS. They may optionally learn about optimizing their HTML and CSS, if it matters for performance of their finished product. Not all sites are the same, after all. The output of Hugo is static HTML (and CSS, js if used, images and other supporting files). The input of Hugo is also static - a collection of HTML templates, CSS and, usually, Markdown text files as the primary content store. Creatively used, Hugo sites can appear as feature-rich as many database-driven sites and in a manner that you simply could not do armed with only an editor, unless your site is only a handful of pages. Any Hugo site can be configured to generate other representations of the site, too, automatically. You probably think that's nonsense, but then again you probably also do not publish a hand--crafted [Atom](https://spf13.com/index.xml) or RSS feed to go along with your hand-crafted HTML. Hand-crafted does not automatically mean better. Even the simplest Hugo site implementation typically makes use of categories or tags (or both) to help readers find other relevant content. Inserting a new page into an existing hierarchy of categories and/or tags is trivial. Edit a file; tag it. The navigation structure is rebuilt, in milliseconds, whether there are five pages or five hundred. [Steve Francia's site](https://spf13.com/) provides examples of these facets in use. With Hugo you can also produce large documentation sites/subsites, and even more importantly, maintain them. The [Let's Encrypt documentation site](https://letsencrypt.org/docs/) is a textbook case study. It's too bad the `vim` project DOES NOT use a tool like Hugo, because then its documentation would stand a chance of being current instead of: > The [VimDoc project](https://www.vim.org/docs.php) has links to various types of Vim documentation. The online, hyperlinked copy of the documentation is currently outdated. Send in the drones to edit. "Currently" has lasted a long time! Another example: [Linode's documentation site](https://www.linode.com/docs/) is generated by Hugo (according to the meta attribute inside, v0.83). You can see the source code for all their documentation, including the site theme and Hugo specifics, here https://github.com/linode/docs. Shocking, isn't it? A tool being used for productivity! You portray using a productivity tool like Hugo as being somehow lazy. That's ridiculous. It's a powerful tool that happens to scale from the simplest of use cases to the complex, and for every use case, makes it possible to produce far richer sites than is possible completely by hand. And all of that without a database or need for a runtime language on a server, or client. A generated Hugo site has no need for PHP includes or other helpers. It can run on the simplest HTTP server; it's just static content. It's a tool, like an editor is a tool, to make an author more productive.

Hugo has seen success with corporate customers, including 1Password, Linode Digital.gov, KeyCDN, and Let’s Encrypt, to name just a few. Bjørn Erik Pedersen took over as the lead maintainer in 2015 and continues to lead Hugo’s thriving community.

Besides the official Vale style guides Buildkite, Linode, and Write The Docs have rules online that you can copy into your repo or use as inspiration for your own rules.

- https://github.com/linode/docs

So after shopping around a bit I found a simple, dependency-less static site generator called Zola. The lack of dependencies sounded very attractive after all the headaches trying to update my Gatsby modules. I wanted to give Zola a try and see what tradeoffs I would need to make coming form a React-based framework to this Rust-based generator.

I think you're thinking about Zola: https://github.com/getzola/zola

But yes, if I were to recommend something, it'd be Zola given that there's just one executable that you need to run and there's absolutely no setup required.

If I were to start again from scratch, I'd likely use Zola as SSG (https://www.getzola.org/)

I've used Zola (https://github.com/getzola/zola) for a static project homepage a few years ago to showcase examples with a simple description and a wasm app embedded in the page, it worked perfectly for me and the docs was clear on how to use it. It was very easy to set up along with a GitHub action to automatically update the wasm binaries when needed. It is definitely a tool I keep in my mental toolbox as a good default.

I'm currently learning https://www.getzola.org/.

It's more manual than idy like but it's gonna be for a small personal and work website so I don't mind much.

It's super fast.

Doesn't seem to fit your use casr but still.

(Note: that list is overwhelming; you don't need to go through it. Order by popularity and look at the top 3-5 at most. Hugo, Jekyll, Gatsby... Personally I'm using Zola [ https://www.getzola.org/ ] for a couple of sites, but that's just me.)