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

Time tracking dashboard with HTML, CSS and JavaScript

Linh Nguyen•170
@auri222
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?
  • Can build a neat HTML structure, and use CSS grid feature to overlap content
  • Know how to import data, build function and use string literal in JavaScript
What challenges did you encounter, and how did you overcome them?
  • Most of the challenges that I faced come from layout (like how to use grid for this, how to overlap the image, etc...)
  • One more problem is from import data to use:
import data from './data.json' with { type: 'json' }

This is the easiest way to import data and works fine on Chrome, Edge and Opera, but Firefox does not support it.

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

Is there a way to load data in JavaScript easier and all browsers can work well on?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sudhanshu Thapa•200
    @Sudhanshu943
    Posted 9 months ago

    very nice.

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