In reply to Brad Dalton.

I should mention, I'm a moderator at the WordPress Stack Exchange

It's not that simple.

For one, any user past a certain reputation can create tags, it's not a sign of official support. I could delete that tag, but it would be recreated by another user at some point. That being said it also serves a purpose.

Questions about WooCommerce are off topic on WPSE, as are all 3rd party plugins and services. Questions must be about WordPress development, to ask a question about a plugins 3rd party APIs and usage wouldn't be a good fit for the site, and there are better places to ask those questions ( e.g. the plugins support ). That doesn't mean WooCommerce is always off topic.

For example, if someone needs to add something to a filter in WooCommerce, but doesn't know how filters work, or if someone says they read that WooCommerce uses post types, what are post types? Questions that require WordPress knowledge to answer, not WooCommerce specific. These kinds of questions can be tagged as WooCommerce, and can get answers without WooCommerce knowledge, and can be useful to all involved.

But a question such as how to empty the cart, or give different prices to different countries, those are valid Woo questions, but they're out of scope, and get down voted and closed. Such questions would be in scope on the proposed WooCommerce site, and if such a site existed, questions could be migrated there, so that WooCommerce developers can answer them, avoiding the down vote and close situation.

At WordPress Stack Exchange we've discussed that we're happy to help, guide and encourage use of the proposal to get the site up and running. We're pointing new users to the proposal when they ask WooCommerce questions and trying to explain. Not every user casting close votes does this though, and it's a lot of work given we're not paid employees, but we try. At the end of the day there just isn't enough WooCommerce expertise on the WordPress stack to answer all these WooCommerce questions if they were left open, and a WooCommerce specific stack was the best answer.

Now that i'm an Automattician, and that Woo has been acquired, I hope that I can encourage other Automatticians and WooNinjas to participate, but at the end of the day Automattic can't assign a handful of people to work on answering questions at Stack Exchange, aside from the friction and problems that can create at Stack Exchange, like most agencies services and companies in the WordPress space, we already have jobs to do. People need to freely contribute their time.

I'm glad that Matt linked to the proposal recently, and I'd be glad of anyone who participates and helps. Any WooCommerce stack exchange that succeeds will need a lot of cooperation with the WordPress Stack Exchange, and we're happy to do that and help bootstrap things at the start.

Right now the proposal has gained the followers it needs and only requires new questions :) If you're curious how Area51 graduates new Stacks you can look here:

http://area51.stackexchange.com/faq

Finally, we have chatrooms on Stack Exchange, and if you're curious you can join the main WordPress Stack Exchange at LoopChat here:

https://chat.stackexchange.com/rooms/6/the-loop

Most of the highest ranking users and moderators idle in that room. If you'd like to discuss the site, there's a Meta site were we discuss changes and answer questions about WordPress Stack Exchange here: