A lot of our thinking at edX about how to live in a multi-service world has been to try to keep everything about a service in the repo for that service. I know this doesn’t jibe with how things are organized today (for example, Ansible playbooks in a central repo), but it is where we’d like to go.
My own strategy for documentation is to try to keep the words near the things they describe. This makes it easier to keep the words in sync with the code, easier to find the words when they need updating, and easier to know the words exist and need updating!
It’s harder to find the words to read, but tooling can help solve that problem as part of the publication process.
So I’m not sure a centralized doc repo with settings for edx-platform is the best approach. What else could we do? Is there a reasonable way to document the edx-platform settings in the edx-platform repo?