Is it okay to use webapps.se as the FAQ for our product? We have a web application that is used by thousands of users (but not millions like Google, etc).
I'm sure it would be considered a "web application" by this site's definitions. But I'm not sure if it would be the right use of webapps.se to use it, effectively, as our FAQ repository.
More explanation:
We're switching around our support system, and I was wondering if we could use webapps.se as our main FAQ repository instead? We would still use the correct QA format and follow all the usual rules for quality posts, etc.
I'm sure it would be considered a "web application" by this site's definitions. But I'm not sure if it would be the right use of webapps.se to use it, effectively, as our FAQ repository.
More explanation:
We're switching around our support system, and I was wondering if we could use webapps.se as our main FAQ repository instead? We would still use the correct QA format and follow all the usual rules for quality posts, etc.
I'm looking into using webapps.stackexchange.com as a support forum for our product Orangedox for Dropbox. Since I'm a big fan of Stack Overflow I would rather use a product like this, where anyone can answer the question, instead of the usual product specific forum.
The idea is to simply provid...
I'm being told here that I don't need to identify myself every time I answer a question about a product I work on, that I should just add the info into my bio. I have done this.
This seems important enough to have a documented policy and a standard method of disclaiming, but I can't find that d...
