Twitch Documentation on StackOverflow

API
2

As I mentioned in the Irc, PLEASE:

  1. Keep the github documentation for endpoint information. Explain usages, example request/response data, etc there
  2. Use stack overflow ONLY for implementation questions / expanding on github api information for language specific contexts

Github is WAY better for document centralization and information dissemination. Stack overflow (Even the document stuff) is WAY better for Q&A, historical retention and visibility [of questions], along with upvotes for good working solutions.

Please keep these two concepts clear cut and separate, otherwise twitch api documentation is going to be a nightmare to read.

2 Likes