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

Time tracking dashboard (HTML + CSS + JavaScript vanilla)

less
P
Antoine•330
@super7ramp
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 think implementation works as expected and is pretty close to the design.

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

🤔 Populate sections using data.json?

✅ fetch data and create the appropriate elements with Document.createElement and a section template.


🤔 Filter according to the selected timeframe?

✅ Use a bit of JS to enable/disable the CSS class corresponding to the right timeframe.


🤔 Implement the section icons?

✅ I did it like this:

  1. Put the icon in each section::before content
  2. Adjust position using position: relative and top and left offsets.
  3. Adjust clipping with overflow: clip and overflow-clip-margin.

It's not perfect - I didn't find out how to get the exact offsets from the Figma design - but it looks good imo.

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

Any feedback/advice welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,350
    @MarziaJalili
    Posted about 2 months ago

    You've nailed it, no cap! 👑

    🌟 A quick win for better UI?

    ✅ If the value of the hours is 1, it might not be really good to display 1hrs, bro.

    ✅ To fix this you can simply put a ternary to render either 1hr or (0, or numbers larger than 1)hrs as follows:

    const hourStr = num === 1 ? “hr” : “hrs”;
    

    ✅ Then, life is easier using a template string you can render the text:

    <time class="current-duration">${timeframes["monthly"].current}${hourStr}</time>                
    

    Other than that, the web’s lit! 🔥

    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

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