-
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
Site Editor: improve flow for creating a new template part #41008
Comments
cc @jameskoster since you have other explorations on creating new template parts and @jorgefilipecosta since you've worked on the quick inserter piece of this and might have thoughts. |
We can prioritise patterns for semantic template parts, but I'm not sure about general ones. The scope is vast which makes it difficult to provide helpful suggestions. In general I agree that we can re-use elements of the existing empty header / empty footer block experience. It may need some adjustments though – perhaps pattern selection can occur in the initial modal when you input the template part name and select the area. |
I feel that short term we should re-enable the inserter |
Also see #37524 |
Agreed, if users elect to create a general template part they will see a blank canvas, and even if they select header / footer they can still 'start blank'. |
I think we can combine:
new.template.part.mp4You'll notice the "choose a name" step is omitted. If the user selects a pattern we can probably go ahead and use the pattern name for the template part. If they don't, placeholders like "Untitled Template Part" are probably fine because requiring a name up front adds a lot of unnecessary friction. |
Whew that feels LOADS better, @jameskoster. Thank you. The lack of inserter is present in 6.0 RC2 and it feels pretty important to fix. I'll comment on the PR from @carolinan to see if we can get that in. |
What problem does this address?
Currently, when you head to the Site Editor > Template Parts > Add New, you are dropped into an empty experience without even a + button to orient you. This feels like a fairly jarring and underwhelming UX:
no.+.buttons.mov
What is your proposed solution?
The text was updated successfully, but these errors were encountered: