[PAGES-58] Don't show component chooser if there's only a single component type you can add Created: 15/Jan/16  Updated: 17/Mar/16  Resolved: 15/Feb/16

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4.4

Type: Improvement Priority: Neutral
Reporter: Andreas Weder Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: page-editor, quickwin, support, ux
Remaining Estimate: 0d
Time Spent: 2h 35m
Original Estimate: Not Specified

Issue Links:
causality
is causing PAGES-64 Ask a user where to add a new compone... Closed
dependency
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: AX: improve page editor
Sprint: Kromeriz 31
Story Points: 5

 Description   

If there's only a single component type you may add to a specific area, I don't want to see a dialog asking me to pick the type of component to add.

We should only show the component selector and open the dialog, if at least two types of components can be added to an area.



 Comments   
Comment by Andreas Weder [ 15/Jan/16 ]

I've linked issue MGNLUI-3692, which asks for the dialog to be changed here to actually be extended, so that the user may also pick, where exactly a new component should be added - examples are at the top or at the bottom.

When we implement an improvement for this issue, we must make sure that picking that location is still possible. Two possible solutions I see are:

  • We offer two "add component" actions in the Action Bar (but not elsewhere), one for adding the component at the top of the area, one at the bottom. These actions could then be smart enough to only show their dialogs, if a user has to pick between more than one component type.
  • We make the choice of the location described in MGNLUI-3692 optional and configurable. It could be turned off to trigger the improvement described in this issue. If it would be on, however, the improvement would be disabled.
Comment by Richard Unger [ 15/Jan/16 ]

+1 !

Generated at Mon Feb 12 06:15:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.