Closed mcdonnelldean closed 8 years ago
@mcdonnelldean — gotcha, that totally makes sense. tables definitely bring in some difficulty, especially with responsive web design (they weren't really built to be that way), so I could lean for something else that will be easier to style and maintain. I've actually spent some time today to make what we have a little bit better on smaller screens, see below:
taking what you've said into account here's what I'm proposing:
table
to div
let me know what you think and I'll get that done. (relates to #50 too)
@thefoxis That all sounds and looks perfect. Couple of notes,
I'd say focus on user bits and leave the sidebar until last. I think it's a good idea though, looking at some apps I use myself on mobile it seems to be the standard alright.
@mcdonnelldean — thanks for pointers :+1:
search-dropdown-active
, turn it back to display: block
to see styling for the dropdown search resultsI think I've addressed everything in this issue, feel free to open more granular issues if there's something I've missed or has to be amended :v:
Post demo we've had requests to make the UI around searching and dealing with the user more refined. We basically need,
@thefoxis I'm keen to see how this will fit on mobile. Ultimately it's just a searchable list of users. If the table format is too restrictive I'm happy for you to comment it out and add in a hardcoded list that better suits our need, we can very quickly break down into components to make it work as needed. We are talking about the possibility of 10,000 users; I'm keen ensure the user experience is not impacted by this scale, even on mobile, so I'd rather you had no restriction to tables on this.
We may have a view more fields to come yet so I would probably edge more towards a searchable 'card' view but we need to have as many rows on screen as possible too.