Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Time Tracaking Dashboard - React.js, responsive CSS Grid layout

react, accessibility
Lucca Rodrigues•430
@ChromeUniverse
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi FM people! Here's my solution for the Time Tracking Dashboard challenge. 😄

Comments:

  • This one took a while to finish but I think I managed to get the UI looking pretty close to the design.
  • CSS Grid really came in handy when building the layout and toggling between desktop and mobile views!
  • This was also a great opportunity to practice React too, as it made it a lot easier to implement to sidebar menu and display the data for each timeframe.

Questions:

  • One of my biggest hurdles was trying to get the big text in the cards (e.g. 10hrs, 103hrs, etc.) to somewhat scale along with the cards and main Grid container - in the end, I ended up using a mix of vw, fixed pixel size and a min() operator to get a somewhat dynamic font size without making it look too ridiculous on large desktop monitors. How can I approach this?
  • Any ideas on some cool animations that I could add to this design? And how could I approach implementing them?

Any extra feedback would be greatly appreciated too! 😉

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Lucca Rodrigues's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.