The big thing is just defining where things are, and what they are for.
- Github: API Documentation, Error reports (API down, returning invalid results, etc)
- Forums: API/Chat/Whatever discussion, talk about things you’d like to see, etc etc. Something that requires back and forth
- Stack overflow: implementation specifics, generally language specific, multiple examples for any given endpoint, etc.
The problem arises when you move something that is extremely well suited for a platform (IE: high level api calls, non language specific that shows the request json/response json from github to stack overflow = bad)
Having stack overflow have examples for /streams using ‘Javascript’, ‘Jquery’, ‘PHP’, ‘C#’, ‘Ruby’, ‘Python’ … is great - and exactly what a good implementation of the stack overflow docs is perfect for.
That way the github can have example request/response json, and ‘See language specific examples at [stack overflow link]’