-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Swap template UX: include initial Page template option #54572
Comments
I dig that. Right now, it's just not clear how to get back if someone is trying to just explore what's available. |
What if "Reset" was "Default template"? |
If it was default template, could it be a permanent fixture in the dropdown, and the selected template could have checkmarks next to it? |
Agree that "Use default template" works better than "Reset".
I don't think it really needs to be – the template name is already displayed as the button label. That label might communicate when the default template is in use though, e.g.:
|
+1 to default template and/or simply listing it in the overall modal itself where we are pushing folks to explore swapping templates. |
That would be ideal, but I think there were some gnarly prohibitive technical issues. @ntsekouras can confim. |
Yes, there is no good way currently to get the default template of a page right now. That's why we use |
When writing the next call for testing for the FSE Outreach Program, I noticed that when switching templates, the Page template (the initial choice) isn't visible in the swap flow. The only way to go back to the Page Template option is to select "reset" which is confusing language when creating a page (makes me think the whole page will be reset: #46859)
swap.template.flow.mov
Can we either include the Page Template as an option in the template selection modal or a clearer "reset" mechanism also within the modal? As it stands, my first instinct was there was no way to get back to the original Page Template. @WordPress/gutenberg-design @ntsekouras
The text was updated successfully, but these errors were encountered: