Show HN: Git-based front-end interface for Hugo (github.com)
I built simple Git-based CMS for Hugo static site generators.
No backend, no database, no configs. Just login with Github, select your repo and start editing.
If you use Hugo for blogging, feel free to check it out at https://github.com/arashthr/hugo-flow
> Why did you make it? I wanted to be able to write posts on my phone, and it's not easy to do that with Markdown. Adding images is also always a headache: copy them, minimize and compress them, remember the correct syntax for images, and type the path.
> How did you make it? I used Google Stitch for the design and Antigravity for coding.
> What about alternatives? Check out Front-end interfaces page in Hugo website. None of them is as simple and dumb as I wanted.
> But is it actually working? It's not perfect, but it works well for me. You're welcome to open issues if you find problems.
11 comments
[ 2.6 ms ] story [ 42.7 ms ] threadhttps://github.com/gollum/gollum/wiki
This is pretty simple and dumb :-)
Maintaining the side on a PC became tedious.
Netlify made life easier by emoving dependency on a local machine and offering an online CMS -- but the UX of editing is very irksome and not conducive to writing.
There were a few nagging bugs in the Netlify CMS editor -- like cursor always jumping to end of line if you are trying to edit in middle of a line. I finnaly fixed this bug by spending 30 mintes with Claude Code.
But yeah -- I have been meaning to build my own online CMS to allow frictionless editing and blog posting. Will either use this or take some inspiration from this for sure. Good work - looks nice!
Also you say it’s git-based but it depends on GitHub. GitHub is not git. What if I want to use another git forge or god forbid a local repo?
I have a similar thing but it doesn’t assume GitHub and is coded in Python (by hand, it’s like 100 lines of Python and flask). Serves my needs! Simple and dumb.
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.
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.