time-tracking-dashboard

Community feedback

• 

  P

  Eli Silk•640

  @elisilkPosted about 1 month ago

  Hi 👋 @KMS56135,

  Congrats on a great solution. 👏 It looks almost exactly like the design.

  When you are ready to dive in further 🤿, I'd suggest a few things related to how the solution works at viewport widths between 1440px and 375px.

  First, when I tested your solution out, I noticed first that at 375px, your solution's height can go beyond the viewport height and so is off the screen (at least for my smaller screen 📺). I'd suggest in your dashboard class, changing the height: 100vh; attribute to min-height: 100vh; instead. That way the container fills the entire viewport, but is not prevented from scrolling.

  Second, testing out your solution at around a viewport width of 940px or so, it starts to get cramped and extends beyond the viewport (without scrolling). And then it continues to get more cramped until it switches over to one big column at 375px (as in the design). I can imagine different approaches to handle this kind of thing. Although maybe not the most flexible solution, adding a couple more breakpoints with media queries would be relatively simple to do. For example, you could move your dashboard container down to one column sooner (while keeping the stats-grid as is), so that the profile and time periods are on top but the stats grid stays at 3x3. Alternatively, you could move the stats-grid__inner down to two columns (from 3) earlier and keep the profile on the left for a little longer. Or do some combination of those two moves before you finally get down to one full column for the whole dashboard. To facilitate this, I'd suggest removing from the .dashboard class the attribute grid-template-rows: 518px; so that your dashboard is free to extend further in the vertical direction.

  Anyway, just something to consider if you are thinking about improving on this solution. 🤔

  Happy coding. 💻

  Eli

  Marked as helpful

  0