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

Time tracking dashboard build with React

react
P
Serhii Orlenko•415
@grifano
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 proud of how I structured the project and organized the components effectively. I also improved the UI, particularly for tablet navigation, by implementing React Router to enable smooth switching between different data views.

Next time, I’d aim to spend less time on CSS. I realized I spent too much time fixing minor visual issues that weren’t critical to the overall functionality.

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

One of the biggest challenges was working with CSS. I had to completely rewrite the styles for the InfoCard component to match the design as closely as possible.

I also realized I need to keep building more React apps to gain confidence. After taking a long break to work on another project using plain HTML, CSS, and JS with Vite, I forgot some React concepts and had to relearn them.

What specific areas of your project would you like help with?

I would really appreciate it if you could review my code and provide feedback on how I can improve it for my next challenge. I want to make my work cleaner and increase my chances of landing a job.

I’m also wondering where to focus my time next: should I spend more time polishing my React skills, or after improving my understanding of Redux, should I dive deeper into Next.js? I’ve heard that Next.js is a more powerful and efficient way to build websites and web apps, offering great performance and high SEO rankings.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mpass•230
    @Benson0721
    Posted 5 months ago

    Your code is amazingly clear to me, and it has helped me understand the concept of CSS Modules and a more component-based way to structure a React app. The only thing I can remind you about this practice is that you forgot to add your icons, which isn’t a big deal.

    As for the next step in learning, I noticed that you have already completed multiple React projects. Maybe it’s time to start another exciting journey with Next.js?

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