Closed danielgolden closed 4 years ago
Here's what I'm thinking right now. I'd bet that a lot about this plan is going to change, but if I have to put this on pause I want to know where I left off.
Feedback welcome! Next up, I'm going to be working on high-fidelity mockups.
Thanks for digging into this @danielgolden . Really appreciate your interest in cleaning up the layout and visual style. Your proposed layout is more vertically compact, which I like a lot.
One factor I want to pay attention to on this is staying true to the controls available in the NR1 SDK / UI Toolkit. Couple of questions for discussion:
No problem, @fightingmonk :). This is really helpful and great feedback. I'm going to include my responses below:
I'm working on this between other projects so I haven't been able to spend as much time on it as I wanted to the last few weeks, but hopefully I should be able to get out a high-fidelity mockup soon and post it here so we can iterate on that. Thanks again for your feedback @fightingmonk!
@fightingmonk I think the changes you've made have worked out great. I've been meaning to create a more high-fidelity mockup that's based on the wireframe from above for a while and was finally able to create it today. I'd love your thoughts on what I'm proposing in this mockup:
Edit: Just for clarity, I'm 100% willing to submit a PR for the design changes we settle on, whenever we get to that step. Just wanted to clarify that in case I hadn't mentioned it before.
p.s. It was great to meet you in person a few weeks ago!
Per @danielgolden 2.5 weeks of duration in and around other tasks. Awaiting feedback from @fightingmonk
@danielgolden :100: on all the table changes you're suggesting! IMO you're describing exactly how it should work.
I'm not sold on the options bar proposal, partly because it's not a pattern I've seen used in the NR product UIs and putting them off to the right detaches them from the IA flow of the page. Would it be more consistent to use another Select element for them immediately to the right of the Filter picker?
i.e. the options bar would be [SLO picker] [Tag picker] [Value picker 1] [State picker 2] and then the loaded N applications could be right-justified as it's just informational.
Good feedback on all points. Thanks, @fightingmonk.
The options bar is mostly a design pattern found in 3rd party nerdpacks because we do not have access to the global header where some of the items found in the options bar could live.
I have plans to work on this update which I'll submit in a PR next week (project load permitting). As Joel mentioned I think it will take about 2.5 weeks to go from start to completely finished (pr feedback changes and all).
:tada: This issue has been resolved in version 0.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Summary
It doesn't look like this nerdpack, as useful as it is, has had much design attention up to this point. A thoughtful redesign would improve the user experience by quite it a bit, so I'm going to take some time to work on a redesign that I can recommend in a PR.
Desired Behaviour
Exactly the behavior that it already has, but with the application of ui design best practices and a visual style that aligns matches that of NR1.
Possible Solution
A redesign! Wireframe and mockups to come in the comments...
Additional context
This matters to me because I think it's important that the open source applications that we release as an org meet our standard of design and UX. Most/if not all of the folks building these apps aren't designers. This happens to be my specialty, so here we go!