Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Awkward wording in "not yet deployed" message #2511

Open
nealrichardson opened this issue Jan 3, 2025 · 2 comments
Open

Awkward wording in "not yet deployed" message #2511

nealrichardson opened this issue Jan 3, 2025 · 2 comments

Comments

@nealrichardson
Copy link

This reads awkwardly to me:

Image

Maybe "Link an existing deployment" or "Link an existing project"? Or something better.

@dotNomad
Copy link
Collaborator

dotNomad commented Jan 9, 2025

Maybe "Link an existing deployment" or "Link an existing project"

A worry I have with the "link" language is that it is not publishing focused. "update" helps connect with what a user already wants to do while using Publisher - publish an update to an existing piece of content.

What do you think of something this?

Is this content already deployed? Update the existing deployment.

Or is the "update" wording the bit that reads awkwardly to you?

@nealrichardson
Copy link
Author

"Link" doesn't sound wrong to me because that's all I'm doing when I click that link: I'm saying "here's the content on Connect I've already deployed, associate this workspace with that". But regardless, we're making assumptions about what "the user" is thinking when they see this. I'm sharing my experience having seen this as a user, that this looks jargony and off, but I'm also probably not the most typical "user". The solution is probably not for us to debate word choice but instead to do some actual usability testing and see how it plays in the wild.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants