Skip to content
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

When there are no synced patterns, the first pattern screen is empty and boring. #52317

Closed
carolinan opened this issue Jul 5, 2023 · 10 comments · Fixed by #52531
Closed

When there are no synced patterns, the first pattern screen is empty and boring. #52317

carolinan opened this issue Jul 5, 2023 · 10 comments · Fixed by #52531
Assignees
Labels
[Feature] Patterns A collection of blocks that can be synced (previously reusable blocks) or unsynced [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable

Comments

@carolinan
Copy link
Contributor

What problem does this address?

On a fresh WordPress installation where there are no synced pattern created, the first screen when you select
Appearance> Editor > Patterns is empty:

Empty pattern screen

What is your proposed solution?

Can we use this area to "promote" pattern creation?
And maybe even link to documentation.

@carolinan carolinan added [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable [Feature] Patterns A collection of blocks that can be synced (previously reusable blocks) or unsynced labels Jul 5, 2023
@00travelgirl00
Copy link

Maybe a little welcome message with a button for "create a new pattern" in addition to your suggestions?

Do you mean with "promote pattern creation" the pattern library?

@carolinan
Copy link
Contributor Author

I meant the first, add a second "create new pattern" button.

@annezazu
Copy link
Contributor

annezazu commented Jul 6, 2023

@WordPress/gutenberg-design to consider as part of the release cycle!

@jameskoster
Copy link
Contributor

In lieu of a nicely designed empty state (which may not be feasible for 6.3 given the time we have), could a short-term solution be to select the first non-empty category?

@carolinan
Copy link
Contributor Author

Yes

@ndiego
Copy link
Member

ndiego commented Jul 10, 2023

Just checking in here since Beta 4 is tomorrow. Do we think we can reasonably get this done for 6.3? Or should we punt?

@richtabor
Copy link
Member

I don't think we could come up with something measurably better that would make a big difference in this short time.

But I'd appreciate if folks added ideas to this issue on how we could present an empty state that was insightful/an intro to patterns perhaps.

@jameskoster
Copy link
Contributor

The current behavior feels pretty buggy imo. "No patterns found." is a bit contradictory when patterns clearly exist?

I don't know if there's time, but it'd be nice to either:

  1. Skip to the first category that has patterns.
  2. Include the "My patterns" category, active, with 0 count. This would at least contextualise the "No patterns found" message (which could be updated to say "You haven't created any patterns yet").

@annezazu
Copy link
Contributor

There doesn't seem to be a clear decision here from design. Let's punt. Moving now.

@richtabor
Copy link
Member

Include the "My patterns" category, active, with 0 count. This would at least contextualise the "No patterns found" message (which could be updated to say "You haven't created any patterns yet").

I like this approach.

@github-actions github-actions bot added the [Status] In Progress Tracking issues with work in progress label Jul 11, 2023
@priethor priethor removed the [Status] In Progress Tracking issues with work in progress label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Patterns A collection of blocks that can be synced (previously reusable blocks) or unsynced [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

7 participants