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

Responsive time tracking dash with CSS grid

Tarek Islam•220
@tarekul
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?
  1. Responsive Design: Implemented media queries to ensure that the layout adapts to different screen sizes, enhancing the user experience across devices.
  2. Dynamic Data Handling: JavaScript to fetch and display data from a JSON file demonstrating understanding of asynchronous programming and data manipulation. The ability to update the UI based on user interactions (like changing timeframes) is a great feature.
  3. User Interaction: The addition of event listeners for the timeframe buttons allows for interactive elements that enhance user engagement. This makes the dashboard more dynamic and user-friendly.
  4. Modular Code Structure: Organized your JavaScript functions (like updateCards and addEventListeners) in a way that promotes readability and maintainability. This modular approach makes it easier to understand and update the code in the future.
  5. Use of Modern CSS Features: The use of features like clamp() for responsive font sizes leveraging modern CSS capabilities to create a more flexible layout.
  6. Error Handling: Implementation of error handling for the fetch ensuring that users are informed if there are issues loading data.
  7. Active Class Management: The management of the active class for the timeframe buttons enhances the user experience by providing visual feedback on which option is currently selected.
What challenges did you encounter, and how did you overcome them?
  1. CORS Issues: When fetching data from a local JSON file, encountered Cross-Origin Resource Sharing (CORS) issues when trying to load the file directly in the browser. This required setting up a local server to serve your files over HTTP.
  2. Dynamic Data Handling: Managing dynamic data updates based on user interactions (like changing timeframes) can be complex. Ensuring that the UI updates correctly and reflects the right data without introducing bugs can be challenging.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ghozy•280
    @Ghozy165
    Posted 5 months ago

    nice

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