[MGNLUI-8639] Styling improvements to pages and assets app grid Created: 20/Dec/23  Updated: 05/Feb/24

Status: Open
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Low
Reporter: Laura Delnevo Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: searchx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Status - i14b.png    
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: SearchX 1. In-App search & Top Nav

 Description   

ACs

  • Include indeterminate state in the table header checkbox, when one or more objects (but not all) are selected on the grid this implementation is dependent from MGNLUI-8679 spike.
    • Currently there's 'all selected' and 'nothing selected'
    • Aim is to have
      • #1 'all selected' (check icon) = select all state
      • #2 'something selected' (hyphen icon) = indeterminate state
      • #3 'nothing selected' (empty checkbox) = unselect all state
  • Remove page icon
  • Page Name and Title to be a single column
  • Add non-applicable (N/A) status label to the status options
    • This should be used when the content doesn't follow the publishing workflow (e.g.: external dam assets)
    • Accompany the N/A label with a icon that on mouse hover show tooltip explaining what N/A means
  • Remove ‘Page’, ‘ABn test status’ and ‘Tags’ columns from pages default. The ‘Page’ column is redundant in any scenario.

 

Design notes:

Depending on what we find from MGNLUI-8679 spike, the 'select all' feature can only exist in search results view of be removed all together.

 

Designs:

N/A status label screen mockup
N/A status label component
Checkbox states component



 Comments   
Comment by Patricia Rodrigues [ 31/Jan/24 ]

sang.ngo Design review: 

  • As mentioned on MGNLUI-8649 the 'indeterminate state' of the checkbox needs to be added when something is select on the grid.
  • Also, there's a new update on the status labels (when the workflow is not applicable to the object), we need to create a new ticket for that cc/ldelnevo 
Comment by Patricia Rodrigues [ 02/Feb/24 ]

Description updated!
And also strikethrough the ACs that were already implemented to avoid confusion.

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