Set up support on stackexchange for various CMSs

[rfay]

What happened (or feature request):

Stackexchange is probably one of the absolutely best support vehicles in the world: Good solutions are properly highlighted and live on and are easily searchable on google.

I'd suggest that we move our primary support channel to drupal.stackexchange.com (for Drupal) and similar venues for Wordpress and TYPO3. That means we'll need tags, and we'll need people to subscribe to the tags.

I was thinking about this in regard to the idea of a Freshdesk FAQ, and I think Stackexchange is ever-so-much better than that. And if we focus our support there, the quality of responses will rapidly rise.

What you expected to happen:

How to reproduce this:

Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.

Anything else do we need to know:

Related source links or issues:

Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

[rfay]

Info on this from stackexchange: https://stackoverflow.com/help/product-support - They want us to be clear about pointing people there for specific types of questions, but handle bug and feature requests in our issue queue.

[rfay]

Our tag is created: https://stackoverflow.com/questions/tagged/ddev

[rickmanelius]

Good to know regarding the delineation between questions and bugs/features. I assume we'll call this closed when we update our docs to direct people to this location in addition to our issue queues / Slack?

[rfay]

We now have

• A tag on Stack Overflow
• Notifications in Slack when questions are created
• I get email notifications from Stack Overflow as well.

#779 PR adds Stack Overflow to our support offerings and will close this out when it goes in.

[rickmanelius]

LGTM and looks like the PR is ready to merge/close as well. Thanks!