jssm VS gutenberg

https://github.com/StoneCypher/jssm

I find the DSL much easier to wrap my head around than the json format of Xstate.

By example, my hobby library JSSM has currently 4904 unit tests that get run in 14 different contexts, and 1.3 million unicode tests that get run in eight contexts.

I use tsc to compile and rollup to bundle

Javascript State Machine

By the way, this is written in Typescript, and type protections are used extensively.

Here's the test directory for one of my things.

This is my general approach

Case study 3: Zola

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.