Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 30 days ago

Time tracking project using JSON

Babs-unique•210
@Babs-unique
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 am proud that I was able to learn how to use JSON file as a JavaScript developer since this was my first time and I am proud of it

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

I face a lot of challenges while trying to use the json file format to display element in my page using the dom

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

All areas that needs refactoring

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • dali987•250
    @dali987
    Posted 28 days ago

    Hi! You did great overall! There are just a few small remarks that I wanted to make.

    • For some reason the images in the cards and the font arent loading and i get errors in the console for each icon used... also i copied the whole project in my local side and it worked ecept the self care icon (since it has a space so you have to replace the "-" with " " for it to work with the .replace() function)

    • there is a typo in the js where you added "e" (third line) (btw it doesnt do much but i told you about it anyway)

    • the site is not responsive for tablets (from 725px to 425px) which is not great so work on that!

    • when i hover over a card the image decides to show its hidden parts (the parts out of the card), just add "overflow: hidden;" to the "user-action-details" class to hide the parts out of it

    • a button doesnt look great when it doesnt have a hovering effect, so add that. All you have to do is to add this:

    button:hover{ /* using the button instead of a class because you didnt give the buttons one*/
        color: white;
    }
    

    and add "transition: 0.4s;" to the button (you can change the duration if you want) and it will have a nice hovering effect

    • some of the sizes and font-weights are not matching the template but its not a big deal so yeah you can ignore this one

    • when i try to hover over a card with developper tools in my browser i get weird stuff happening (2 cards starts flashing)

    For the most part you did great job! happy coding!

    Marked as helpful
  • P
    Ralph Angelo Gonzaga•190
    @codejeroo
    Posted 28 days ago

    Hi great Solution! However if I may add, it's better to look up the design in various screen sizes. From what I can see, it has quite problems in tablet screen-size and mobile screen size. Your containers tend to overlap. You can fix this and adjust this by setting breakpoints using media querries and fixing it with CSS. Overall nice solution!

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub