EDIT: Let's try this again (again). We're about community, and this one's been passionate about its needs. Please go check out the third (and hopefully final) chapter in the naming trilogy.
Both the Community and the Community Team have spent a lot of time actively discussing this Meta post:
★ A better name for our site ★
Unfortunately, after agreeing that a change to "WordPress Development" made sense, as posted here, additional internal conversations have convinced us that the change would help with some problems, but cause others, and we're not comfortable making a name and design change that we think lacks long-term viability.
It's painful to be conveying a reversal here. But we owed it to you to do so as soon as it became clear that we have more work to do to solve the problems that made you want a change in the first place.
- We agree that Wordpress Answers... ain't great. We need to help figure out something better.
- We realize that the community needs a better way to instantly communicate that the site is really dedicated to problems in running or working on a Wordpress.org site, not those having problems with Wordpress.com.
The problem we have with "Development" is that many people not already active in the site misinterpreted what that meant. Many people assumed that it meant that people who are administering WP.org sites, but who don't actually ever manipulate code, were in the wrong place. Some even assumed it was a much narrower site, for those working on the open source project itself.
At the end of the day, we felt it would cause potential new users to bounce before they realized that some of them are exactly the kind of experts you want.
I'm genuinely sorry we didn't do a better job ensuring comfort before announcing the change. We can do better, but we believe in this site too much to stick with a call we think may hamper its long-term prospects to attract more experts.
So, here's my question: What are the key things the header needs to convey to address the very legitimate concerns the community has?
My sense of what we need to communicate is the following:
- The site is for questions about programming or administering wordpress.org sites.
- The site is not for problems that are limited to wordpress.com
Is the above complete? Is it missing anything? We really want to get this right for you, so I want to start by ensuring we have decent consensus on what we need to convey (other than a dislike for the word "Answers" ;), and then we can work on proposed suggestions for names and/or bylines that will communicate what we have agreed are the key things the community is about.