Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Time Tracking Dashboard with editable, stored values (React)

react
HelloTechTinu•670
@tinuola
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?

This could have been a straight-forward project, but I opted to modify the project for an extra layer of challenge by adding interactivity.

The Daily records/stats can be edited and stored for that specific web browsing session. TO EDIT DAILY STATS: In the daily view, click on the ellipsis icon to open an update form.

The edit/form option is only visible in the daily view, and the project includes logic to make sure total Daily values add up to no more than 24 hours.

If I did start over I would do more pre-planning about managing the state of the app globally rather than at the component level, and design a more elegant form/UI for the update process.

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

The decision to make the daily values editable immediately introduced complexity to the project, and I had to learn about how to use the Web Storage API to persist/store updated values.

Theming was also another area I wasn't very familiar with and had to read about. Initially I was aiming to have theming also be decided by a viewer's OS and preferences, but that turned out to be more involved than I cared to explore for this project. But when I do, I'll probably return to update the theming functionality. So for now, it's a hard-coded toggle rather than dynamic switching based on other factors.

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

Given the level of state changing, the app could do with added accessibility. Pointers to good articles/tutorials about how to approach accessibility in React applications would be welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on HelloTechTinu'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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.