Hi everyone,
I’ve been using Hugo for several years now, and every year I write hundreds of posts with it. Most of what I write is not IT-related, but law, social commentary and general writing. So first of all, I really want to say thank you to the Hugo community for creating such a great framework. Hugo has been very important in my own writing workflow.
Over the past few years, however, I kept running into one recurring problem: my writing workflow depended very heavily on VS Code on my computer. I tried a number of other approaches, but most of them did not really work well for me. In particular, I wanted something that felt simpler and more direct when I was away from my usual desktop environment.
To solve that personal problem, I spent some time learning, preparing, and experimenting, and eventually I built a small application for myself:
PocketHugo
GitHub repo: GitHub - h2dcc/pocket-hugo: PocketHugo is a mobile-friendly editor and publishing workflow for Hugo sites that store content in GitHub. · GitHub
Homepage: Pocket Hugo
This is actually my first real project, so I know it is still very rough in many places, especially compared with the level of experience and technical depth of people on this forum. I’m sharing it humbly, mainly because it solved a real problem for me, and I thought maybe it could also be useful for someone else who has a similar need.
The basic idea is simple:
- edit Hugo content directly in the browser
- work with a GitHub-hosted repository
- stay compatible with Hugo-style content structures
- keep the workflow usable on desktop, tablet, and phone
At the moment it supports things like:
- GitHub sign-in and publishing back to a repo
- three Hugo-compatible content structures
- loading already-published posts back into the editor
- local draft recovery
- image upload, compression, and WebP conversion
- optional timed auto-commit for drafts
- page editing / quick timeline style writing
It is mainly intended for people who want a browser-based workflow while still keeping a fairly direct Git + Hugo content structure, rather than using a more traditional CMS model.
I’m not claiming this is broadly useful for everyone, and I’m definitely not claiming it is the best way to work with Hugo. It is simply something I built to solve my own problem. But if anyone here has had a similar need, maybe it may be worth trying.
If anyone is interested, I would be very grateful for any feedback, suggestions, or corrections. Since this is my first project, I’m sure there are many things I still do not understand well.