IMPORTANT: the difference between this proposal and others previously posted:
the proposal is addressing only those technology tags which have their exact SE sites already. The complete list: raspberry-pi, drupal, joomla, blender, magento, emacs, wordpress, tex. Nothing more. No ambitions to categorize tag unix. But why questions with the above tags should still end up at [SO] without any warning given? ([SO] should stop drawing the momentum from its own children.)


Why we allow to create Stack Overflow technology spinoffs if we then let them stand in shadow of Stack Overflow when it comes to their topics?

Let them give a gift from their parent to start their career.


For the above mentioned limited set of Stack Overflow spinoffs, implement simple tag-to-site recommendation map.
Example for actual [SE] sites and [SO] tags:

joomla.stackexchange.com <-- joomla, joomla3.3, joomla2.5
emacs.stackexchange.com <-- emacs, emacs24, emacs23, dot-emacs
arduino.stackexchange.com <-- arduino, arduino-uno, arduino-ide, arduino-makefile
wordpress.stackexchange.com <-- wordpress, wordpress-3.9, wordpress-4.0, wordpress-plugin


On submitting the question, if a tag for recommended migration is detected, submit action will get intercepted by dialog asking:

Based on your tag(s) {tag-name}, the question may be more appropriate to ask at {site-name} site of Stack Exchange network. On dedicated site you might get faster response times and more helpful answers.

[Continue submitting at current site] [Cancel]

If necessary, the first paragraph would be repeated for each target site. For example, tags , will show two paragraphs (joomla.stackexchange.com and drupal.stackexchange.com)


Primarily Stack Overflow site.


  • many questions will become asked on correct sites solely by effort of their OP's
  • a relief for moderators who will get less requests for moving of questions
  • topical sites will receive their questions which currently end at [SO]
  • moderators and fans of topical sites won't need to monitor [SO] so much, putting comments please ask at othersite.stackexhange.com but they could stay more focused at those topical sites
  • topical sites would gain their momentum more quickly, especially those in BETA


Some time ago I decided to help joomla.stackexchange.com with redirecting the traffic from [SO] as few other users from joomla.SE site already do. The reason was that I found that the community of gurus at joomla.SE is more avid than at [SO]'s tag where I found many unanswered questions, a good soil for [badge:tumbleweed] in many cases. After OP's got the comments and moved their questions to topical site, they received their replies within one day. But I find such a monitoring as unnecessary as it is helpful because it could be partially automated. And this is why I wrote this proposal.

  • I'd like to hear from downvoters their view why downsides of this proposal outweight its upsides.
    – miroxlav
    Jan 24 '15 at 17:39
  • @random - Hi! The main difference between questions you linked and my question is that they were too expensive to implement because of their sophisticaed algorithms. But I'm addressing only "hard map" of technology tags (joomla, windows phone, emacs, etc.) which give no doubt about migration and have their SE sites. (And is easy to implement.)
    – miroxlav
    Jan 24 '15 at 17:52
  • Don't see the difference between setting a flag in the database and providing a hard map, which the other questions suggest
    – random
    Jan 24 '15 at 17:58
  • @random - honestly, I don't get what in this case 'setting a flag in database' will do. Other questions want to categorize also ambiguous tags like Unix. I don't agree witch such complex and expensive approach. I'm suggesting only obvious cases based on existing SE sites. Tell me, why those questions suitable for topical sites should still end up at Stack Overflow without any warning given? Are you sure this area cannot be innovated at least by adding something basic?
    – miroxlav
    Jan 24 '15 at 18:06
  • 1
    I know it's just an example list but you should probably remove Windows Phone from your list, programming questions are off-topic there.
    – PeterJ
    Feb 7 '15 at 4:13
  • @PeterJ - removed, thank you
    – miroxlav
    Feb 7 '15 at 11:10

You must log in to answer this question.

Browse other questions tagged .