vavalos5
commented
1 year ago Today was spent chatting with Chris, Gina and Justin to collect use cases and pain points. Please see notes below:
Eric:
“We’re cataloging and grouping on what the key things are for. We’re collecting some web and product designs as of right now to just get a better understanding of what is going out with other teams Capture just the designs - more of the ladder, can we come up with a place we’re going to, enough detail of its viability For now its where do we need to go and if we need to add or change components to Grommet then we will do that
Chris: Shared examples of some layouts he’s recently worked on Justin will have a more accurate layout of the cards and Gina may have a better accurate layout of the list view Hub page is common, some form of list, there might be some form values and details, take into consideration when there are thousands of tasks on a list, is a list or a card view better? It would be good to consider that Chris is trying to boil it down templates into these buckets that accommodate the experiences Making sure as we walk through a hub to a list to a detail are we hitting the right beats, are they going to satisfy the right needs, where does the flexing need to be to help us to give a variety without having to make too many templates AI, brand elements, general types of templates
Gina/Justin:
One of the problems we often see within services is Navigation - how might we simplify some of the layouts so we don’t feel the need to have everything in one view like the Cloud Services screen Typography would be good to look at as well - Gina shared screens where she changed the headers from our text-strong color to a grey so it isn’t so harsh. She also changed the name-value pair styling How do we change the behavior of where grids and layouts are better used? IF DS is too prescriptive, we need to be able to be flexible based on the content so UX Designers can best leverage layouts. What’s the best way to avoid designers from interpreting the templates DS creates differently over time? What are some areas where we are failing at providing great navigation and letting the user know where they are? ( See Dashboard example Justin shared) Why are we wasting so much space? Why are we center aligning everything? Responsiveness is not great as you get down to smaller screens. For example, cards are not fluid and rather stay the same width through out each size. What would we want to show?
I've also already started capturing a variety of screens of different layouts from GLCP, Compute.
Started categorizing them by 1 page, 2 page, 3 page, 4 page layouts
Awaiting screens from Diane, possible others from Sylvia, Amanda and Megan.
L0ZZI
SOjaHPE
ericsoderberghp
Figma File
Problem Statement
Designers and developers would be able to deliver faster and more consistently using detailed, design system aligned page templates that could be copied and pasted.
Pain Points:
How might we provide designers page templates that could be easily utilized quickly within Figma for their designs?
How might we determine the correct taxonomy for each Page Template type so our users can quickly find and utilize them?
How might we determine which Page Template(s) should be prioritized based on needs?
How might we provide visual examples to show them useful information when creating page layouts?
Deliverables
Future Next Steps
Some Questions
Summary of Findings
In the Figma file, I was able to determine the top 3 most commonly used page layouts : 1 column, 2 column, and 3 columns. There are some examples of how content may be laid out based on use cases gathered from GLC, Compute, and Storage. It is even broken down further by:
Lastly, the 2 column dashboard example is broken down to 3 different page templates: simple, with nested grids and an other.