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

Improvements to Synced Patterns #27890

Open
10 of 15 tasks
mtias opened this issue Dec 24, 2020 · 5 comments
Open
10 of 15 tasks

Improvements to Synced Patterns #27890

mtias opened this issue Dec 24, 2020 · 5 comments
Labels
[Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) Needs Design Feedback Needs general design feedback. [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.

Comments

@mtias
Copy link
Member

mtias commented Dec 24, 2020

It's been a while since we gathered thoughts on where to take reusable blocks next. With the work that went into template parts — and particularly #27887 — the experience is going to be radically improved and several longstanding bugs removed. There are some design updates needed to accommodate some of these changes (no direct "edit / save" flow) and to improve the clarity of reusable blocks in general but let's also look into other ideas that can improve the different user flows related to them.

@mtias mtias added Needs Design Feedback Needs general design feedback. [Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. labels Dec 24, 2020
@paaljoachim
Copy link
Contributor

paaljoachim commented Jan 7, 2021

Adding the following issue to the list:
Add content alignment option into the main reusable block toolbar
#17640

There is also a bug related to the above issue. If one converts a Full width or Wide block to a reusable block the alignment option is also adjusted to the default Reusable block width. #8288

@Tropicalista
Copy link

About my issue linked here, is it possible to add a reducer on https://github.com/WordPress/gutenberg/blob/da8555d258edbe676fa079fb51252f918ae032e1/packages/reusable-blocks/src/store/reducer.js

to let know the block is just been converted from a reusable block?

@NewYorkerLaura
Copy link

Just adding to the discussion here. In 5.7.1 creating new reusable blocks experience is disastrous. Their primary functions have been stripped away. I've had to roll over 100 client sites back to 5.6.3. It is a UX disaster. The best feature and the strongest selling point to clients of the Block editor is now non-functional

  • I have no ability to name a block
  • Lots of "untitled blocks" doesn't let me know which one I want
  • I am unable to edit the block if my boilerplate has changed and have those changes iterate across the site (kind of a disaster in a where my call to action purchase buttons across 50+ pages are now a right pain to update)
  • I am unable to break a block out into regular blocks if I want a one-off change or are using the reusable block as a template

See attached video:

https://trainingvideoslaura.s3.amazonaws.com/reusable+block+not+working+on+PELC.mp4

@mtias
Copy link
Member Author

mtias commented Apr 26, 2021

The ability to name a block upon creation is addressed in trunk and should remove the case of having a bunch of "untitled reusable block" names:

image

@jameskoster
Copy link
Contributor

jameskoster commented Aug 25, 2022

A possible consideration for inclusion here: #43261

Edit: Tracked in #43598 instead.

@annezazu annezazu changed the title Improvements to Reusable Blocks Improvements to Synced Patterns Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) Needs Design Feedback Needs general design feedback. [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Projects
None yet
Development

No branches or pull requests

5 participants