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

css grid, fetch API, responsive design

accessibility
Itoro (Celine) James•200
@CelineJames
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Williams Akanni•350
    @shadowbanks
    Posted 5 months ago

    Hello Itoro,

    Congrats on completing the challenge 🥳, great work 💪🏿

    Here's my review

    • Active menu: The active menu isn’t working on the first render and only activates on mobile views. You might want to look into fixing this.
    • Responsive Layout:
      • Between 500px - 700px width, part of the content gets cut off, I'd recommend using media queries to target medium screen size for better responsiveness.
      • For the height above 859px, the profile and work cards are the only ones expanding to fill extra space. This seems to happen due to using grid-template-rows: repeat(2, 1fr) for mobile view. To address this, you could add grid-template-rows: repeat(7, 1fr) to the media queries targeting mobile devices, so the addtional space can be evenly distributed.
    • Console logs: It’s a good idea to comment out the console.log statements in your JavaScript for cleaner code.
    • CSS Tip: You can create a common class for the card divs to avoid repetition. For instance, you could add a .card class and use it to apply common styles across all cards:
    .card{
      background-repeat: no-repeat;
      background-size: fit;
      background-position: top right;
    }
    

    This will help you avoid repeating the same code for each card.

    I hope these tips are helpful. Keep up the great work, and happy coding :))

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