(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.
Just like many others, I also have this problem: it’s getting harder and harder to find the articles I’ve read later.
There’s so much great content I come across every day that, in my experience, it’s rather difficult, if not impossible, to find it again by searching Google.
So I started building a personal solution to keep the stuff I read searchable.
There are existing tools that try to solve this, but I have some unique requirements that pushed me to create my own. Things like Telegram integration, weekly summaries, and indexing YouTube content.
More importantly, I felt the pain enough that I was motivated to work on it as a side project.
A good example is the frustration and disappointment I had with Pocket: the search functionality was terrible, and each update seemed to make the product less usable.
I’ve now got a working prototype, and I’m putting on the final touches. Let me know if you have any thoughts, or email me if you’d like to try it out.
I also like to add "Pragmatic Thinking and Learning: Refactor Your Wetware" by Andy Hunt
It can be considered as a followup of pragmatic programmer.
For me the main challenge is to how to stay relevant in days of constant change, and the best answer seems to be constant learning. So, let's learn how to learn! And this is exactly the main topic of this book.
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.