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

Time tracking dashboard

next, tailwind-css
P
Raul•240
@luAr26
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

  • Aakash Verma•9,500
    @skyv26
    Posted 6 months ago

    Hi @luAr26,

    Great job on your project submission! 🎉 It’s clear you’ve put in considerable effort, and I appreciate the work you’ve done. Here’s some constructive feedback to help you refine your project and elevate it to the next level:


    1. Hover Interaction Missing 🎯

      • While it’s okay for practice, hover interactions were a requirement for the challenge and are crucial in real-world projects. Paying attention to these details will help you become a more detail-oriented developer. ✅
    2. Responsive Design Issues 📱

      • Between 640px and 1020px, the design doesn’t provide a good user experience. Improving this breakpoint will significantly enhance responsiveness and ensure a smoother experience for users across all devices.
    3. Heading Hierarchy Consistency 🔢

      • Maintaining proper heading hierarchy is essential for both accessibility and SEO. For example:

        <div>
          <h1 className="text-[0.9375rem] font-normal leading-[1.2] text-subtitle sm:mt-[40px]">
            Report for
          </h1>
          <h2 className="mt-1 text-[1.5rem] font-light leading-[1.166667] sm:text-[2.5rem]">
            Jeremy Robson
          </h2>
        </div>
        
        OR 
        
         best way
        
       <div>
         <h1 className="mt-1 text-[1.5rem] font-light leading-[1.166667] sm:text-[2.5rem]">
           <span className="text-[0.9375rem] font-normal leading-[1.2] text-subtitle sm:mt-[40px]">Report for</span>
           Jeremy Robson
         </h1>
       </div>
      

      Consider reviewing your structure to ensure semantic and hierarchical consistency.

    4. TypeScript Best Practices 🛠️

      • Move your TypeScript types and interfaces into separate .ts files, then export and reuse them wherever needed. This approach makes your code more maintainable and scalable.
    5. JSON Handling Scalability Tip 🌐

      • Instead of creating a separate file for JSON to JS object conversion, consider using the fetch API to serve the JSON dynamically. It’s scalable and aligns with modern development practices. (This is just a suggestion for your knowledge!)

    I hope this feedback is helpful and gives you actionable steps to improve your project. Keep up the great work, and don’t hesitate to ask if you need further clarification or assistance! 🚀

    Best,
    Aakash Verma

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