-
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
Inserter: Reorder blocks in the Theme & Design sections #36547
Comments
For "theme" blocks, header, footer, navigation, post lists should all be coming ahead. |
What blocks do you think should be prioritized for the |
We probably need to move some of those in "design" to "theme" (site title, logo, etc). |
+1 to grouping all theme blocks together. Then we can consider hiding that entire category in the post editor. |
FWIW I find both "Theme" and "Design" to be a little blurry. I'm not sure the nuance will be interpreted so well by the average user. "Design" also feels a little loose as a definition... the arguments to classify the blocks therein can probably be made for the majority of blocks... Here's the Design section with the Theme blocks removed: Columns, Group, Row, Spacer, and Separator feel like Layout blocks and will see frequent use in both post and site editors. Page Break and More Link feel like content formatting and will not feature in the Template Editor at all. Buttons... I'm not sure, seems to be a bit of an outlier :) All that said, would it make sense to rename "Design" to "Layout" and include the blocks above? Then create a new section for Page Break / More Link that is only visible in the post editor. Then find a home for Buttons :) |
I removed myself from assignee because my first approach wasn't the one wanted and I understand the issue is time sensitive. I'll still try to find a better approach but If anyone has something better in mind, please try this out. |
Reorder so that the most common use cases are on top.
Reference images:
The text was updated successfully, but these errors were encountered: