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

Time tracking dashboard solution using grid and javascript

AllisonFavour•170
@AllisonFavour
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?

Handling the manipulation of the DOM and populating the UI with the appropriate data.

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

Populating the DOM with the JSON data. I initially wanted to render the UI using Javascript but i realized it was less efficient in this case, so i decided to structure the HTML and use css to style them and just manipulate the neccesary parts of the UI with JS

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

I am proud of using CSS grid and Javascript to complete the challenge

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Lovro Peraić•420
    @loki-pepe
    Posted 5 months ago

    Well done. I think your HTML could have been written a bit better semantically and there is an issue with your CSS.

    I can't comment too much on it since I've never used SASS, but the main problem is when you set the font-size of the :root element, you inhibit the user from setting a default size in his browser settings, which would be troublesome for visually impaired users. I would recommend not touching the font of the root element and just use rems assuming the default size is 16px.

    Also, your sizes don't really match with the design, and the whole UI should be centered, so you could do with a few tweaks if you wanted to make it perfect

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