Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Time Tracking Dashboard Main

EL harabiy•250
@Mubarak-Adeyemi
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I’m most proud of implementing a fully responsive design and using CSS Grid effectively to create a clean, organized layout. Next time, I’d focus on optimizing JavaScript for better performance and explore adding more interactivity, such as allowing users to customize their tracked activities.

What challenges did you encounter, and how did you overcome them?

I found it difficult to arrange the cards in the desktop view while ensuring smooth accessibility and optimizing SEO. I strictly adhered to semantic tags and ARIA labels. To overcome this challenge, I wrapped all the elements in a container, allowing for better structuring and layout management.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ilya Andreev•880
    @NeoScripter
    Posted 9 months ago

    Hey! I checked your solution and it's nice that you adapted it to different screen sizes. I haven't done this one myself so I'm not sure what functionality it should have. However, one thing I noticed that you can improve is your profile picture proportions. Currently, it's distorted due to the image adjusting to the container size. What you can do is put the image into another div and set on the image the properties object-fit: cover and object-position: center. It should fix the problem. I hope it helps!

    Marked as helpful
  • Graiess_Youssef•410
    @graiess073029
    Posted 9 months ago

    Hey ! The solution that you made is simply amazing. I was admiring how it was responsive as i opened it from my phone ans it fit perfectly. So, the only advice that i can give you is to increase the height of the main div (the div which contains the time-choosing bar and the card as children) to make it identic to the design. And that’s it, i wish that i helped you.

    Marked as helpful

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.

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