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

HTML, CSS with Flexbox and Grid, and JavaScript.

P
Carlos Eduardo Santos Oliveira•180
@Carlos-Eduardo-S
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 to have completed the project, implemented the interaction with JavaScript, and used JSON. Since it was my first time using JSON, I enjoyed working with the tool and was glad to complete the project using it.

What I would do differently is write the code in a more simplified way. I believe my code turned out too lengthy.

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

The interaction with JSON, since it was my first time using fetch, was a bit more challenging. But after studying a bit and doing some tests, I was able to use it easily, and the project went very well.

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

I would like help both with the code itself — how I can simplify it — and, especially, whether I could have done something differently with JavaScript, or if there’s a way I could have made it simpler.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Mirko Zlatunic•250
    @mirkozlatunic
    Posted 2 months ago

    great job to have the styling so it looks good to me. what I suggest to change is the following:

    • Try not to repeat the code for each button click
    • Set on of the button to default

    Here is an example that I did:

    // Fetch data from the JSON file
    fetch('./data.json')
      .then((response) => response.json())
      .then((data) => {
        // Render cards with the default timeframe (e.g., "weekly")
        renderCards(data, 'weekly');
    
        // Set "Weekly" as the default active button on page load
        const weeklyButton = Array.from(buttonEl).find(
          (button) => button.textContent.trim().toLowerCase() === 'weekly'
        );
        if (weeklyButton) {
          weeklyButton.classList.add('active');
        }
    
        // Add event listeners to buttons for dynamic updates
        buttonEl.forEach((button) => {
          button.addEventListener('click', () => {
            const timeframe = button.textContent.trim().toLowerCase(); // Get the timeframe (daily, weekly, monthly)
    
            // Remove the active class from all buttons
            buttonEl.forEach((btn) => btn.classList.remove('active'));
    
            // Add the active class to the clicked button
            button.classList.add('active');
    
            // Re-render cards with the selected timeframe
            renderCards(data, timeframe);
          });
        });
      })
      .catch((error) => console.error('Error fetching data:', error));
    
    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, SASS, 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