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

Time-tracking-dashboard

Bunchydo•570
@Bunchydo
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’m most proud of being able to complete the project and successfully figure out how to use JSON in JavaScript. It was a great learning experience and made me more confident in working with data formats and client-side scripting.

Next time, I would spend more time researching solutions and approaches rather than trying to rely solely on memory. This would help me explore more efficient techniques and potentially avoid certain hurdles.

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

One of the key challenges I faced was understanding how to parse and manipulate JSON data within JavaScript. Initially, I struggled with how to dynamically access and update nested properties.

I overcame this by reading documentation, experimenting with code, and using online resources to deepen my understanding of JSON structure and JavaScript methods. Breaking the problem into smaller pieces and testing solutions iteratively also helped.

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

I would like feedback on:

Code structure and readability: Are there any ways to make my code more maintainable or easier to understand? Best practices with JSON and JavaScript: Am I following efficient and standard methods when working with JSON, or are there better approaches I should consider? Debugging techniques: Any tips for debugging dynamic data issues more effectively would be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Trần Thành Danh•1,500
    @TranDanh1122
    Posted 7 months ago
    1. about UI/UX rule, SEO rule: you need default data when user visit on page, let make daily active at default and load data of this type
    2. JSON data can use fetch to load, you need to learn it because that what people do in real life project!
    3. You need to load data dynamic, base on title and property name (like "title", "daily"), not the order (0, 1) because in big project, when backend have a bit change on their API, we dead, absolutely dead!
    4. you can let [var1, var2] = ["#id1" , "#id"].map(el => document.getElementByID(el), that will clean you code
    5. "daily", "weekly" just a type of filter, try load data like i mention in "3", that will /3 you js file size
    6. check my solution, that not best, but i think you can find some idea these
    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