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
Remove the launch button and resume regular functionality in the editor, and observe analytics and user testing.
I know we have the "focused launch" flow starting from this point; the goal is to expand that flow to other places as well and not depend on this one button.
Explore other placements for launch. Better design placement for this action might be within the FSE site editor. We might even have some earlier designs around.
The text was updated successfully, but these errors were encountered:
Let's remove the launch button in the editor for now and have another round of design work to find a better placement for it.
We have enough subjective evidence that the "launch" button in the editor header is confusing customers:
Issues After page edit: not obvious what "Launch" does #52590 "Launch" button is confusing #52561 Gutenboarding pre-launch: Update CTA button label in the editor #41211
Internal & user testing bring this up frequently (recent p1621458244077600-slack-dotcom-pod-design-selection and p58i-avT-p2)
Layout breaks easily, even on bigger screens, especially with languages where texts are longer (Gutenberg mobile editor: Misaligned Header items #50758)
Translating "publish" and "launch" has been challenging (p1604066018174600-slack-luna):
The above has since been updated, but terms are still often close at quick glance and show how this might be challenging in other locales as well:
Context
Initially, when designed & implemented (#39048), the "Publish" button was relabelled as "Save" because it was causing issues with React (#42508).
Adjusting terminology is challenging because it's coming from the core (pbAok1-BD-p2), and needs to be updated in quite a few places to be consistent.
We also have few other areas where people can launch their sites:
Frontend preview
Settings (though this is hidden for sites with WP-Admin nav unification views enabled)
Site setup checklist (excluding Atomic sites but that's being fixed, see Atomic sites don't have site setup checklist enabled at customer home #50523)
Next
The text was updated successfully, but these errors were encountered: