-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
NUX Tip Confusion: Tip misses nuance of pre-publish flow #9256
Comments
Would appreciate your thoughts @karmatosed. This applies even if tips are scaled back as suggested in #9242. |
I am very OK with iterating on Tips, what would you suggest? |
I guess the simples way to address this issue would be to the change the copy to something simpler like "Finished writing? That’s great, let’s get this published. Click the “Publish” button." That does not pass wrong information to users, would that be ok? |
As long as we're updated language, I wonder about changing "writing" to "drafting" to be a little broader; not everyone who publishes writes. Two options: Short and sweet: More detail to set expectations: |
This looks like it will be resolved with #16131. Once that PR is merged, let's close this issue. |
@mapk That does improve some confusion, but the language is quite specific to text-based content by using "readers." It also doesn't address the nuance of publish/schedule. In #16131
Proposed
|
#18041 has addressed this by removing dot tips in lieu of a welcome guide modal. |
Describe the bug
The final NUX tip points to the
Publish...
button, which isn't a one-click Publish button anymore and really triggers the pre-publish workflow on the sidebar. However, the NUX tip says click "... and you're good to go." It also misses the potential that a user may schedule the post for the future in thatAre you ready to publish?
workflow by saying "lets get this published right now."To Reproduce
Expected behavior
The tip should reflect the control offered the user in this confirmation step. The text should be corrected to reflect current behavior, though not necessarily needing to describe both clicks.
Screenshots
The text was updated successfully, but these errors were encountered: