Definitely look into the cookbook. If we filled the doc with more than just the bare examples there--given the massive length of examples we could make--it'd be a lot harder to find what we're looking for, and things would get chaotic fast.This is the sort of thing I'd love to see in the documentation. More common use case topics. Scrubbing through the docs right now is painful when you aren't sure exactly what you are looking for.
If I'm not mistaken, forking Renpy on github means to fork the repository, or make an individual copy, to use at your own discretion. So PyTom is saying to make your own copy, go into the sphinx/source directory and edit the documentation there (github has a web interface fro editing these things), and then send him a pull request so he can include the changes in the original/official github repository.I'm subscribed to renpy on GitHub...but somehow I suspect that isn't the same thing as forking? Maybe a quick tutorial on how do to it could be good? Also for Mac users as well?
I think this should show how to go about the forking process.
