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

time-tracking-dashboard-main

P
gkilasonia•320
@gkilasonia
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

  • Jay Khatri•4,230
    @khatri2002
    Posted 5 months ago

    Hi @gkilasonia!

    The developed solution looks great!

    Below are some suggestions for improvement:


    1) Center Alignment Issue (Fixed Padding on body)

    Currently, you've used fixed padding to center align the component in the desktop resolution:

    body {
        padding: 253px 165px 0 165px;
    }
    

    While this works for some screen sizes, it fails on smaller desktops, because the padding values are too large, causing unnecessary vertical scrolling.

    Better & Adaptive Approach Using Flexbox

    A more responsive and standard approach is:

    body {
        display: flex; /* Create a flex container */
        flex-direction: column; /* Stack content vertically */
        align-items: center; /* Center align horizontally */
        justify-content: center; /* Center align vertically */
        min-height: 100vh; /* Take full screen height */
        gap: 5rem; /* Provide spacing between content and footer */
        padding-inline: 165px; /* Only reduce width, avoid unnecessary height padding */
    }
    

    Now, remove the fixed padding on body and any margin-bottom on main.
    This ensures the component remains centered across all resolutions.

    2) Use button Instead of p for Clickable Elements

    Currently, the text elements "Daily", "Weekly", "Monthly" are inside <p> tags; and click events are handled directly on these <p> elements.

    While this works functionally, it is not semantically correct because:

    • A p tag is for static text, not interactive elements.
    • A button is the correct element when an action occurs on click (e.g., selection, toggling).
    • Using <button> improves accessibility (keyboard navigation, screen readers).

    3) Missing Hover Effects

    The hover effects for buttons and cards are missing, as per the design reference.
    Consider adding hover effects to enhance the user experience.


    The rest of the solution looks amazing! Keep up the fantastic work! 🚀

    Marked as helpful
  • P
    Gwinyai•140
    @gkuzivam
    Posted 5 months ago

    good work with setting up the web and mobile version

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

Oops! 😬

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

Log in with GitHub