Problem/Motivation
The proposed approach in #2905922: Implementation issue for Layout Builder leverages local tasks to expose layout functionality. This issue is intentionally started from a problem statement, rather than solution.
This is like to create usability issues as:
- This is an overarching task, users might not expect or note it near the node edit links.
- It is not homogeneous to the other buttons, which switch the user into an edit page to edit content.
- It requires nesting of "save" and "cancel" links to be close to the overall action.
Resulting in the following design:
We should explore design alternatives that expose it on the page in such a way that its easy to find, distinct from the other "edit actions" and scalable to include the save and cancel functionality.
Proposed resolution
There are several proposed solutions, include them in the comments.
Remaining tasks
- Explore design directions
- UX and accessibility sign-off on the final direction
- Development
User interface changes
We expect to change the design of the change layout, save layout and cancel layout navigation.
API changes
-