legacy-docs
legacy-docs copied to clipboard
Project-wide documentation.
There are 6 subdirectories of this repository. * about Seems to cover what the project is about and an overview of the components. That I understand. But what is the...
add file: `/language-tracks/documentation/for-contributors.md` Talk about: * track readme * contributing guide * pull request / issue templates
The contribution guides lay out details for getting started and submitting PRs. But it doesn't cover things like PR merging strategies and issue resolution processes on GitHub. So I am...
add directory `language-tracks/tooling/` Can contain a README with an overview, link to the configlet documentation, talk about blazon, probot/stale, and other new bots as we write them.
add file: `language-tracks/exercises/metadata.md` Some of this can be moved out of the ./language-tracks/exercises/anatomy/readmes.md file, and maybe also ./maintaining-a-track/regenerating-exercise-readmes.md
We have: https://github.com/exercism/problem-specifications/blob/master/CONTRIBUTING.md and https://github.com/exercism/docs/tree/master/contributing-to-language-tracks which cover similar ground but were obviously written separately. Is one of these considering more definitive than the other moving forward? Which resource should tracks...
There are things that we do to keep the lights on. Is this the place to document those things too? - availability indicators (API 200s, website 200s) - availability objectives...
This is not documented anywhere that I can find.