You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to propose some content updates to our generic confirmation modal when the user is abandoning changes. For Analytics, Customers, and Products, that modal follows the pattern in the screenshot. (Orders has alternate language for some reason.)
Current:
I believe a more industry-standard and useful phrasing would be to use a question as the header. We can also simplify the language in the body. Right now, the if and then statements are weirdly tautological. (Essentially: "if you delete, then you'll discard")
Proposed:
Note that the "Yes, discard" is a pattern that Google uses, which I like because it makes the header and the button feel like a conversation.
__
I know the team has been working on updates to the contextual save bar pattern. Could this language be a programmatic default as part of those changes? Or are these hard-coded in the various resource pages?
Rationale
Cleaner, crisper, more conversational experience across admin
The text was updated successfully, but these errors were encountered:
Summary
I'd like to propose some content updates to our generic confirmation modal when the user is abandoning changes. For Analytics, Customers, and Products, that modal follows the pattern in the screenshot. (Orders has alternate language for some reason.)
Current:
I believe a more industry-standard and useful phrasing would be to use a question as the header. We can also simplify the language in the body. Right now, the if and then statements are weirdly tautological. (Essentially: "if you delete, then you'll discard")
Proposed:
Note that the "Yes, discard" is a pattern that Google uses, which I like because it makes the header and the button feel like a conversation.
__
I know the team has been working on updates to the contextual save bar pattern. Could this language be a programmatic default as part of those changes? Or are these hard-coded in the various resource pages?
Rationale
Cleaner, crisper, more conversational experience across admin
The text was updated successfully, but these errors were encountered: