Wp-calypso: Should 'Add new WordPress' be changed to say site?
At the bottom of the menu of your sites is an encouragement to 'Add a new WordPress'. This feels weird in the use of the word WordPress as we don't use that anywhere else.
For example:
I would recommend it should say 'Add a new site' or even 'Add a new WordPress site'. I would not suggest this if we set up the language like this in other places, but we don't. As a result this is a confusing use of the word WordPress.
karmatosed
All 8 comments
I think the reason was to normalize WP.com versus WP.org and site versus blog and just have a new noun called "a WordPress."
lancewillett
on 2 Jun 2016
I'd maybe suggest 'site' then as 'a WordPress' I'd suggest probably makes not much sense to users. That is unless there is some marketing/ campaign to set that as a term. Of course, maybe I'm assuming it doesn't and it does.
karmatosed
on 2 Jun 2016
On April 14, we moved the "add new {thing}" to the bottom of the menu bar. At this point, we changed the verbiage from "Add new WordPress" to "Add new site" for _new_ users (in SidebarFooter), but it looks like it was not implemented for existing users (in SiteSelector).
New user example (site count = 1), created today:
After much back and forth and deliberation, and much confusion among users unintentionally creating multiple sites when trying to create new posts or pages, I would like to see it changed to "Add New Site" everywhere. This is much clearer and still gives us a fairly agnostic way to frame website vs blog vs portfolio vs store.
Edit: the original choice to make the switch to "Add New WordPress," i.e. WordPress as a noun, was made in 2014 and labeled an experiment. The goal was to mitigate the confusing dichotomy between website and blog and instantiate a "WordPress" as a way to encompass both and beyond, allowing flexibility especially in light of Jetpack-connected sites. 2 years later, I am comfortable calling this experiment and moving forward with clearer language - in this case, "site," which is also being used in most public-facing messaging as a catchall. I think there is still merit to defining and using the idea of "a WordPress," but I think it's best done in tandem with robust messaging, not in isolation in the application.
meremagee
on 2 Jun 2016
I would also be for usage of Site — either with "WordPress" in front of it or without. It just seems more clear to me. And it should be synced to all places, as @meremagee mentions.
marekhrabe
on 2 Jun 2016
I would like to see it changed to "Add New Site" everywhere
❤️
Emphasis on the everywhere. cc @michaeldcain since I bug him about this. :)
ianstewart
on 2 Jun 2016
All blogs (squares) are sites (rectangles). I think users would understand that they'd be adding another site to their WordPress account. Let's just be consistent _everywhere_. #KeepWordPressProper
michaeldcain
on 2 Jun 2016
If we're worried that users might not understand site vs. blog vs. WordPress, we're definitely not helping by calling it different things within our own UI.
michaeldcain
on 2 Jun 2016
This has bothered me for a while. PR up at #7147.
much confusion among users unintentionally creating multiple sites when trying to create new posts or pages
I think this showed up in one of the user tests for the editor as well.
nylen
on 29 Jul 2016
Related issues
spen
·
3Comments
samouri
·
3Comments
jjchrisdiehl
·
3Comments
ghost
·
3Comments
ehg
·
3Comments
Most helpful comment
On April 14, we moved the "add new {thing}" to the bottom of the menu bar. At this point, we changed the verbiage from "Add new WordPress" to "Add new site" for _new_ users (in SidebarFooter), but it looks like it was not implemented for existing users (in SiteSelector).
New user example (site count = 1), created today:
After much back and forth and deliberation, and much confusion among users unintentionally creating multiple sites when trying to create new posts or pages, I would like to see it changed to "Add New Site" everywhere. This is much clearer and still gives us a fairly agnostic way to frame website vs blog vs portfolio vs store.
Edit: the original choice to make the switch to "Add New WordPress," i.e. WordPress as a noun, was made in 2014 and labeled an experiment. The goal was to mitigate the confusing dichotomy between website and blog and instantiate a "WordPress" as a way to encompass both and beyond, allowing flexibility especially in light of Jetpack-connected sites. 2 years later, I am comfortable calling this experiment and moving forward with clearer language - in this case, "site," which is also being used in most public-facing messaging as a catchall. I think there is still merit to defining and using the idea of "a WordPress," but I think it's best done in tandem with robust messaging, not in isolation in the application.