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

Responsive Time Tracking Dashboard

David Mwalimu•260
@broken555wheel
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?

Styling pages with CSS has got a lot easier and it takes me less time to do than it did when I started. I also use less redundant code.

Furthermore, I at least managed to fetch the data from the JSON file.

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

Toggling between days, weeks, and months, maintaining an initial selection on loading. I solved this by assigning a selector to one of the options then toggling between them by clearing all possible occurrences of the assigned selector and reassigning the relevant option.

I also thought that since the data is consistent across cards, it should be possible to create one component and duplicate it as many times as the length of the dataset, so that if it changes, the UI changes accordingly.

I did not succeed in implementing the above and instead used a fixed for loop based on 'cards' created from the HTML file. This in turn led to the problem of annotating the data value to the already existing content in the element eg for previous time, annotating the hours to Last Week- causing me to use formatted string from the JS file.

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

The challenges mentioned in the previous section.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ayako•430
    @Ayako-Yokoe
    Posted 4 months ago

    Great work! I like the way you fetched the data. As you mentioned in the challenging part, I used JavaScript's innerHTML to render HTML tags and CSS class names with embedded JavaScript variables. Here’s an example:

    card.innerHTML = <div class="contents"> <div> <p>${data.title}</p> ... </div> </div>;

    I hope this helps!

    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