-1

I would like to propose a new stack that will only deal with questions related to WordPress plugins. This isn't for WordPress plugin development questions, but rather, for questions related to setting up and/or using specific WordPress plugins.

The reason behind my suggestion is I asked a questions regarding a certain complex setup using iThemes Security, but it was put on hold with the reasoning that the question is off-topic because wordpress.stackexchange.com is only for questions that are for pure WordPress development, not for third-party plugins. After further discussion, it turned out that this was an issue that the WordPress moderators previously discussed, going back and forth, without reaching a final firm conclusion.

However, I do believe that third-party plugins (and themes) play an integral part in WordPress, and therefore questions about them should not be put on hold immediately.

Therefore, I would like to suggest that a new stack be created, could be named wpx.stackexchange.com (wpx = WordPress Extensions), or could be named anything you like, that will deal solely with questions regarding third-party plugins, such as WooCommerce, W3 Total Cache, iThemes Security, Contatct Form 7, or any other plugin. Again, all questions in that new stack will only be related to WordPress plugins, with some available tags being the names of those plugins. Restrict questions in that stack to plugins-specific questions. Those should only be about plugins that already exist.

If there are questions regarding plugin development, then those should be asked in wordpress.stackexchange.com, keeping it as it is, for issues related to WordPress development only, and not including any question related to third-party plugins.

What do you think? Your input is greatly appreciated.

1

Shouldn't the Plugin Developers provide support for their products? What keeps the Plugin Developer from creating a plugin then dumping all the support onto the WPX Exchange? That could possibly lead to many unanswered or bad questions since it is entirely user based / controlled.

How would you keep the Question to Answer ratio balanced with the large array of WordPress plugins available, 35,571 Free Plugins to be exact? How would you handle Premium Plugins or Plugins that make revenue by offering paid support?

All in all it seems like it could be easily abused and to keep a healthy QA Ratio you would need a very large user base to cover the range of knowledge of the 35,000+ Plugins.

  • 2
    Your argument almost convinced me we should build a site like this. Look at the symptoms — A large number of projects focusing around one subject; each with a disparate community; many of them behind a pay wall? That would make a great SE site. In reality though, disallowing 3rd party support on Wordpress SE is a big mistake. These projects each have communities of their own, and that's a huge area of growth on many sites. Providing technical support works very well as long as they're not trying to outsource their entire "customer support" channel. But that's another conversation. – Robert Cartaino Jan 19 '15 at 15:45
  • 1
    I think the problem of having too many plugins can be sloved by restricting tags to popular plugins first, so unpopular plugins will not have tags of their own. Once there are more questions about a plugin that is becoming more popular, you probably will have someone with enough points to create a new tag for it. This way you eliminate the support issue you are talking about. – Greeso Jan 20 '15 at 12:47

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .