One of the things I like about this particular stack is how cheap and quickly it can be used to create a usable page.

Thanks to Feather Wiki’s tiny footprint, GitHub Pages can receive the updated page and have it ready for consumption within 30 seconds of a successful push. Although the ability to push to remote repos was a premium feature in Working Copy, I felt like it was worth it, especially since it allows me to use the same functionality on other projects, now.

In the vein of other free offerings, I’d like to look into setting up a REST backend that can be used to fill in the type of HTML components that are starting to get tricky to hand write.

I still don’t have a clear idea of where to go, but I’d say first steps would be to find an environment where HTMX does work and try to piece together why it doesn’t seem to work at all on this end.

Maybe I can see if the SvelteKit app works better? It will be easier to set up a proper API path than trying to use the static file method I’ve been playing around with.

One alternative approach I could look into would be to set up Fermyon’s Spin framework. Since this website gets very inconsistent use, it should be exceedingly cheap and provide reasonable speeds.

Since this is a JAMstack app, l’ll need to prove that it can handle web requests without crazy effort. Let’s see which one of our approaches pan out.