Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Time Tracking Dashboard with JavaScript

Chloe•350
@01Chloe
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

  • Nneoma Njoku•1,210
    @SatellitePeace
    Posted almost 3 years ago

    hello @01Chloe nice job i particularly like the tweaks you made to the project

    On screens > 960px the card looks ok, but on larger screen the contents of the cards are overflowing

    • So here is my suggestions instead of using grid throughout, you can use a combination of grid and flexbox

    • in your main container you can have two sections one for the cards and one for the user.

    Display the main container to flex and give the user section a flex-basis of 23%

    • Then you can place all your cards in the second section and use the grid to create columns

    EXAMPLE

    main {
      max-width: 1200px;
      width: 100%;
      display: flex;
      column-gap: 2rem;
      align-items: center;
      justify-content: center;
      margin-bottom: 1rem;
    }
    
    sectionOne{
      max-width: 20rem;
      width: 100%;
      flex-basis: 23%;
    }
    
    sectionTwo{
      display: grid;
      grid-template-columns: repeat(3, 1fr);
      gap: 1.5rem;
      place-items: center;
    }
    
    //the above is for desktop first if you want a mobile-first do 
    
    sectionTwo{
      display: grid;
      grid-template-columns1fr;
      gap: 1.5rem;
      place-items: center;
    }
     - this means you don't need a grid-template-row
    
    • Also avoid giving heights to your card container just give them padding and allow the content to determine the height, this will help prevent overflow

    • Finally, instead of using JS to change the background color of the active button you can use the CSS focus() pseudo class so

    button:focus{
       background-color: #444;
    }
    
    Then you can then use the active class only for the first button because it has to be on focus when the page loads
    
    so
    
    ````
    btnWeek.addEventListener('click', () => {
       boxWeek.forEach(month => {
             day.classList.remove('hide');
         });
    });
    
    btnMonth.addEventListener('click', () => {
         boxMonth.forEach(month => {
            day.classList.remove('hide');
         });
    });
    ````
    
    I hope this helps
    
    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