indiegamedev.org is Live
Introducing indiegamedev.org as an open, community-driven resource for indie game developers built from Markdown and maintained through GitHub.
I’ve been working on a new project called indiegamedev.org, and the initial version of the site is now live.
The idea came from thinking about how much useful information exists for indie game developers, but how scattered it tends to be. Tutorials end up spread across YouTube, personal blogs, Reddit posts, GitHub repositories, Discord conversations, and other places. A lot of that knowledge can be difficult to discover later, and when something becomes outdated, there often isn’t an easy way for someone else to help improve it.
I wanted to experiment with a different approach.
indiegamedev.org is intended to be an open, community-driven resource for indie game development. The site is built from Markdown and hosted openly on GitHub, so articles and pages can be updated over time. If someone follows a tutorial and notices that something has changed, they can raise a GitHub issue or submit a pull request rather than the information simply becoming stale.
TecunHuman will be using the site to index its own work: games, tools, tutorials, articles, videos, and other resources. It gives the studio a place where that work can be organized and remain useful instead of being spread across different platforms.
But the site was intentionally structured so TecunHuman doesn’t have to be the only studio doing this.
Other developers and studios can contribute their own pages, articles, projects, and resources. There is already a contribution guide explaining how the repository is organized and how to submit changes:
One of the things I’m also thinking about early is how this could scale if more people become involved.
The repository uses GitHub’s CODEOWNERS functionality as part of that design. The longer-term idea is that once a developer or studio has contributed enough to establish trust, they could become responsible for reviewing changes to their own section of the site.
That means I don’t necessarily have to remain the person approving every contribution forever.
Instead of creating a community project where one maintainer eventually becomes the bottleneck, I’m trying to build the structure for distributed ownership from the beginning. Studios could maintain their own content while still contributing to a shared resource.
Another important part of the idea is helping information retain its value over time.
A normal tutorial can slowly become less useful as tools, APIs, and workflows change. Because the content on indiegamedev.org is open source, someone following an older tutorial who notices that a step no longer works can do something about it. They can raise a GitHub issue, suggest a correction, or submit a pull request updating the article.
That gives useful content a path to stay useful instead of simply becoming stale and being replaced by another tutorial somewhere else.
I also want the site to become an index for useful work that already exists.
For example, if I create a YouTube tutorial, write about one of my open-source Godot projects, or document something I learned while making a game, I can give that information a permanent home on the site. Other developers could eventually do the same with their own tutorials, tools, games, and resources.
For communication around the project, I’m planning to use places like Discord and Reddit alongside GitHub. GitHub can remain the home for issues, pull requests, and maintaining the site itself, while Discord and Reddit can provide easier places for discussion, sharing ideas, and discovering new contributions.
I’m also interested in exploring automation around publishing. Since the site is built around structured Markdown and GitHub, there are opportunities to automate parts of the workflow - for example, helping turn contributed resources or discussions into articles that can then be reviewed, edited, and maintained like everything else on the site.
There is still a lot to build. Right now I’m working on the structure, design, and initial content, and I expect the site to evolve quite a bit as I use it and as other people begin contributing.
But the initial implementation is live, and it finally feels like the idea is starting to take shape.
If you’d like to take a look at how the site is built or contribute, the GitHub repository can be found here: