Update 11/25: Thanks for your feedback! We're going to go ahead and drop "& Usage" from the site title. The header image and the "official" language around the site (in the help center and about page, for example) should be updated within the next few days.
I know this community would prefer to have the site name in Spanish as well, but that's not a change we're prepared to make at this time.
I'm Laura, a product manager at Stack Exchange.
I wanted to let this community know that I've started a discussion over on Meta Stack Overflow about some general guidelines for naming our sites, specifically our language sites, going forward. Feel free to read and discuss my post over there.
The gist of my proposal is that "& Usage" generally makes a site name longer and more difficult to say and type without adding much, if any, meaning.
We'd like to rename existing Stack Exchange language sites to just "X Language" and drop "& Usage" from both existing sites and any new language sites we launch in the future.
This means the header image on the site would simply read "Spanish Language" rather than "Spanish Language & Usage", and all of the official documentation would drop "& Usage" as well. The site URL would not change.
We've already done this with our Italian Language site (in private beta at the time of this writing), and they were pleased with the simpler name. Until now, our language sites have followed the naming convention of "X Language & Usage Stack Exchange", but why? It seemed to make sense at the time, but as we've grown, it's become clear that "& Usage" isn't really necessary. A site about a particular language is, by definition, concerned with the usage of that language — that's where all the questions come from!
Before we actually make any changes to existing sites, I wanted to hear any concerns you might have. I feel like a shorter, simpler name is a big win for everyone, but please feel free to post concerns about this particular community here, or any general concerns over on the main MSO thread.
it's become clear that "& Usage" isn't really necessary.
more than that, it's plainly dumb. I'm glad that it's being dropped.