This is my first open source project, and I’m excited (and a little nervous) to share it with you.
I love traveling, but I’ve lost trust in traditional review sites. Between SEO spam, bots, and paid 5-star ratings, finding genuine recommendations has become a noise-filtering exercise. I wanted a curated list where the "noise" of anonymous internet crowds is replaced by a transparent commit history.
Git Guide is an experiment in building a community-curated travel directory without a traditional backend or database.
* No Database: The "database" is just folders of Markdown files (countries/Italy/Rome/Eat/best_pizza.md).
* No Servers: It runs entirely on GitHub Actions.
* IssueOps: Data isn't entered via a custom form; it's entered via GitHub Issues with YAML templates.
How it works:
1. A user opens an Issue to propose a place.
2. The community votes using GitHub reactions (/).
3. Once a threshold is met (currently testing with net 100 votes) and a moderator approves, a Python script (running via GitHub Actions) triggers.
4. The script validates the location using geopy (OpenStreetMap), creates the Markdown file, commits it to the repo, and updates the README indexes automatically.
I wanted maximum transparency. If a place is added or removed, you can see exactly who proposed it, who voted for it, and the commit that changed it. There is no black-box algorithm sorting the results.
And I need your help! This is my first real foray into open source. The architecture works, but I have a lot of ideas for the future (better frontend, more complex voting logic, decentralized moderation).
This is my first open source project, and I’m excited (and a little nervous) to share it with you.
I love traveling, but I’ve lost trust in traditional review sites. Between SEO spam, bots, and paid 5-star ratings, finding genuine recommendations has become a noise-filtering exercise. I wanted a curated list where the "noise" of anonymous internet crowds is replaced by a transparent commit history.
Git Guide is an experiment in building a community-curated travel directory without a traditional backend or database.
* No Database: The "database" is just folders of Markdown files (countries/Italy/Rome/Eat/best_pizza.md). * No Servers: It runs entirely on GitHub Actions. * IssueOps: Data isn't entered via a custom form; it's entered via GitHub Issues with YAML templates.
How it works: 1. A user opens an Issue to propose a place. 2. The community votes using GitHub reactions (/). 3. Once a threshold is met (currently testing with net 100 votes) and a moderator approves, a Python script (running via GitHub Actions) triggers. 4. The script validates the location using geopy (OpenStreetMap), creates the Markdown file, commits it to the repo, and updates the README indexes automatically.
I wanted maximum transparency. If a place is added or removed, you can see exactly who proposed it, who voted for it, and the commit that changed it. There is no black-box algorithm sorting the results.
And I need your help! This is my first real foray into open source. The architecture works, but I have a lot of ideas for the future (better frontend, more complex voting logic, decentralized moderation).