I want to bump this topic because I’m interested in working on the documentation myself and I’m wonder if the thought of using a Git repository would be possible. The implementation of the system itself shouldn’t be hard – You all have control over what gets pulled into the official repository that gets displayed online, and it allows the community to help you. I’m currently going through the FPS Tutorial (Programming Guides > First Person Shooter Tutorial) and there’s small things that have changed that make me worry about how old the documentation is. The creation of a project with Basic Code no longer creates “FPSProjectGameMode.cpp”, it’s “FPSProjectGameModeBase.cpp” now. As a developer, I’m looking at this and wondering if the name change means there is an entire restructuring that has happened that makes this tutorial out of date. And even if everything works exactly the same, acknowledging the changes (through proper renaming) is a simple way to prevent doubt in the quality of the system.
I’d like to convert the tutorials into Markdown as a way of giving Epic a data file that they could utilize, but also as a way to allow community revisions. In either case, I’m still going to be going through the tutorial, so I will be marking the changes. I can make a post about those changes, but honestly just being able to send you a pull request would be so much easier.