(Author here) Correction for the title: "Front-end interface for Hugo blogs on GitHub" would be right title.
To clarify, this web application only works with repositories hosted on GitHub. Authentication and repository updates are handled entirely through the GitHub API, which allows the app to remain completely stateless, secure, and configuration-free.
Although the idea of making it more generic by supporting different git providers or self-hosted VPS instances is appealing (hence the initial title), there are already much better solutions out there for that use case (like DecapCMS). The goal here was to trade generality for total zero-setup simplicity.
Author here. You're completely right about the GitHub specific implementation. I made a mistake in the title! Right now only GitHub auth is supported. Although the design should work with any Git repo down the line. Sorry for causing confusion. Unfortunately I can't edit the title now. I will add a comment to explain this limitation.
As for the tech stack, I chose JS because the main goal was a lightweight web UI that handles online editing and easy image uploads, and JS sounded like a better fit. Having said that, I'm also not happy with current state of npm and I will look into an implementation with Go and tmpl.
True. But look at the situation in Iran. As much as internet seems like an essential part of daily life, there is the possibility for the governments to shut it down.
To clarify, this web application only works with repositories hosted on GitHub. Authentication and repository updates are handled entirely through the GitHub API, which allows the app to remain completely stateless, secure, and configuration-free.
Although the idea of making it more generic by supporting different git providers or self-hosted VPS instances is appealing (hence the initial title), there are already much better solutions out there for that use case (like DecapCMS). The goal here was to trade generality for total zero-setup simplicity.