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

Time Tracking Dashboard

Leanne Keenan•140
@leannekeenan
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 was incredibly difficult. The CSS was hard for me in terms of layering the color of the stats container, the image within it, and the records over the image.

The JavaScript was also quite difficult in terms of how to use the specificity of nested arrays to locate content.

Lastly, while I got the project to work, per see, I could not get the values from the JSON file to stay in perpetuity on the DOM - the values flash on the screen when the stat option is selected from the user bar.

What challenges did you encounter, and how did you overcome them?
  1. Layering the stat container, stat image, report container, and the report content all as one object.

  2. Getting the JSON values to stay in perpetuity in the DOM when a stat option button gets clicked.

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

Any help is welcome, but mostly I'm hoping to get help with the JSON values staying on the screen when the stat option button gets clicked.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • ikitamalarose•420
    @ikitamalarose
    Posted about 1 year ago

    First of all congratulations on the effort made

    then I took a look at your GitHub repository but I had a hard time finding my way there are too many files that I don't really know what to look at.

    But I suggest you take a look at my solution on this project and look at the main.js file it could help you understand how to ensure that the data is always there with each click.

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.

Oops! 😬

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

Log in with GitHub