On the Stack Overflow blog ( http://blog.stackoverflow.com ) the drop down for the Stack Exchange is unpopulated. This seems rather odd in the layout and wording.

enter image description here

That said, should this even be on stack overflow or should there be a blog.stackexchange.com (thus why it is on MSE rather than on MSO)? Note the text behind that dropdown:

enter image description here

Compare with the drop down from another blog enabled site that shows the associated community (note: $site.blogoverflow rather than blog.$site):

enter image description here



  1. Move blog.stackoverflow to blog.stackexchange (related: Move the Stack Exchange blog to blog.stackexchange.com )
  2. Associated blog.stackoverflow with meta.stackexchange.com
  3. Make the communities drop down populate stack overflow related sites
  • I don't think the top bar should be there in the first place, it's not possible to be logged in (the blog is not a Stack Exchange site) so it's pointless to begin with. Most likely a design overlook that slipped by. – Shadow Wizard is Ear For You Apr 22 '14 at 19:26
  • @ShadowWizard thats indeed another option... though the top bar kind of makes some sense when you can get to an associated community for the blog. – user213963 Apr 22 '14 at 19:29
  • @ShadowWizard Nope, by design. See my answer. – Adam Lear Apr 22 '14 at 22:50
  • @Anna fair enough, rare case of "agree to disagree" then I guess. – Shadow Wizard is Ear For You Apr 22 '14 at 23:03

blog.stackoverflow and blog.stackexchange are the same thing. There is no site associated with the company blog, so at the moment the "site switcher" just shows a pointer to the site list. We also don't necessarily want to drive folks to Meta from the blog, although that may happen later on as we see how Meta is getting used.

As Shadow Wizard notes in the comments, it's impossible to log in on the blogs the same way you can on a Q&A site, so we can't show notifications and whatnot, but Jeremy's plan was to keep the topbar as consistent across all our sites as possible. This is why we didn't just update the look of it on the blogs (did you know that there was a topbar on blogs before? :)) but also implemented a rather stripped down version of the site switcher.

That said... the wording does come off a bit weird. I'll drop the word "other" from it to make it more fitting.

  • Hrm, now I'll have to consider making Data Explorer completely consistent. :P – Tim Stone Apr 22 '14 at 23:01
  • Well, I think that in this case simplicity beats consistency. Plain link or logo back to the "main" site should be enough, no need in the whole top bar, black and empty. :) – Shadow Wizard is Ear For You Apr 22 '14 at 23:02
  • @shadowwizard I personally prefer not having a dropdown there, but Jeremy won this one. :) – Adam Lear Apr 22 '14 at 23:04
  • I know why he won, it's because you lost your cat! – Shadow Wizard is Ear For You Apr 22 '14 at 23:09
  • Tangental - something to think of when looking at 'what site do we want people to hit' - curl http://blog.stackexchange.com/feed/ shows pages back for <atom:link href="http://blog.stackoverflow.com/feed/" rel="self" type="application/rss+xml" /> and <link>http://blog.stackoverflow.com/2014/04/putting-the-community-back-in-wiki/</link> - its more a consistency thing. (Do you want me going here or there, and if its there, it should be there, not kind of there...) – user213963 Apr 22 '14 at 23:36
  • 1
    @MichaelT Not sure what options Wordpress offers in this regard. Ideally, I think our blog should primarily live at blog.stackexchange.com, but I'm not sure what's involved in making that happen off-hand. – Adam Lear Apr 22 '14 at 23:37
  • @AnnaLear I certainly agree with that bit - blog.stackexchange would fit better. Just one of those branding things that might be done better. – user213963 Apr 22 '14 at 23:41

You must log in to answer this question.