Consolidate project documentation
afeld opened this issue · comments
We currently have documentation about the project scattered around:
which seems like too many. At the very least, I think we can make the messaging more consistent. There are a handful of audiences that we want to speak to:
- Program officers or other potential users / new use cases
- Current users looking to get more information
- New 18F teammates
- Potential outside contributors
- Curious passerby
Questions:
- What can we consolidate?
- Where should different pieces of information live?
- How should it be organized?
Would love some content (and content design) help!
Seems like this was dealt with -- there is no longer documentation in the README, and all of the other links are broken except for docs. Hooray!