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

Time Tracking Dashboard

sass/scss
P
Emmanuel Lopez•480
@EmLopezDev
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 am most proud of pushing through it, there were times where I couldn't figure out how to solve a part of the solution but rather than give up I tried and tried until I figure it out.
  • Getting a better understanding of some of the core concepts of JavaScript like event delegation , the .reduce() method and Promises.
  • Taking in the extra time to create a loading state
What challenges did you encounter, and how did you overcome them?
  • Buttons not working after fetching data. I forgot that fetching data re-renders the HTML causing any event listeners to be removed, therefore I had to use event delegation to get it to work. I figured it out by using stack overflow and reading up on the fetch() method.
What specific areas of your project would you like help with?

I would like some feedback on the main.js file was there a better or more efficient way of writing the js.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alperen Aksoy•150
    @aksoyalpi
    Posted about 2 months ago

    Your HTML and CSS look very good (your solution is also very accurate), but your js is not that performant, because you add and remove a lot of elements. Try to use more css to change the data (for example with data attributes, that helped me a lot; see this: https://developer.mozilla.org/en-US/docs/Web/HTML/How_to/Use_data_attributes).

    My Solution is also not perfect, but you can check it out, if you want to see how to use the data attributes and minimal js :)

    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 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