Yeah, that sort of helpful handling is good. I just didn’t want to re-invent the wheel while I’m reinventing other things. I’m looking at a development progression where you start with client-side-templates because they can get you up and running with almost no support and hacking away in the browser. Then as you need data, you talk to postgREST. Then as you begin to need a backend you migrate the templates into the Rust app server and put any queue handlers in there. Then migrate those queue handlers into dedicated workers. Trying to make each refactoring easy enough that it flows well, but minimal infra needed at each step.