[MGNLUI-3142] Improve usability for template and component selection Created: 09/Sep/14  Updated: 11/Sep/14  Resolved: 10/Sep/14

Status: Closed
Project: Magnolia UI
Component/s: dialogs, page editor, pages app
Affects Version/s: 5.3.2
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Lars Fischer Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: usability, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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:

 Description   

There have been complaints about the usability of the template/component selection dialogs. These are some inspirations on what could be improved:

  • All components must be visible at once. Paging with next/prev is not considered very user-friendly.
  • More useful order of components: Most used components (consider text/image) should appesr on top of the list
  • Grouping of components in categories (Video-Player, Audio-Player, Flash-Player would be grouped in a category)


 Comments   
Comment by Andreas Weder [ 10/Sep/14 ]

I agree that selecting components in the page editor as well as templates when creating a new page could be much improved. I also agree with your suggestions as to what could be improved. There's actually some older design work that covers all the brief use cases you've mentioned:

  • it is capable of showing all templates at once
  • it organizes templates in groups
  • it collects the list of recently used templates
  • it also offers the user to mark some templates as favorites, which are then more readily accessible

These designs are part of a larger flow defining how a new page and a new component are added.

We'd have to revisit these designs before starting any implementation, though, as this work was done in a different context. In essence, though, I roughly recall that the deduced UI would be quite flexible and capable of simplifying its appearance and behavior if only few templates were available, but would still scale up for more complex set ups with dozens of different templates. I'd certainly take it as a starting point for any new work.

Comment by Lars Fischer [ 10/Sep/14 ]

We don't see any chance this will be integrated in the near future. Once there is more demand for these improvements we might come back to this topic.

Generated at Mon Feb 12 09:03:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.