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

Time tracking dashboard

react, tailwind-css
P
Mustapha•200
@Mustapha909
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'm most proud of the project's overall responsiveness and how it adapts gracefully across various breakpoints. Leveraging Tailwind's spacing scale and utility classes allowed us to create a clean, maintainable design that works consistently on mobile, tablet, and desktop. It was rewarding to see the layout transition smoothly between flex directions and grid configurations.

If I were to do it differently next time, I would invest more time into creating custom breakpoints and possibly a design system for even more granular control over the UI. I might also integrate more advanced state management or even animation libraries to enhance user interactions further. This experience reinforced the importance of flexibility and planning for responsive design from the start.

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

One of the main challenges was ensuring that the layout remained fluid and centered across a wide range of screen sizes. Initially, the flex direction and absolute positioning of certain elements (like the timeframe buttons) caused the content to shift or get clipped at specific breakpoints. To overcome this, I revisited the responsive classes in Tailwind and adjusted the breakpoints, using a mix of flex and grid utilities to ensure that the design gracefully transitions from a column to a row layout. This helped maintain a centered and cohesive look regardless of screen size.

Another challenge was fine-tuning the dynamic sizing of components. It took some trial and error to set up the spacing scale so that the user profile and activity cards scaled proportionally on different devices. Leveraging Tailwind’s utility classes for width, height, and spacing allowed for quick adjustments until the desired responsiveness was achieved.

Overall, the process reinforced the importance of responsive design and iterative testing across multiple breakpoints. Each issue provided an opportunity to learn more about Tailwind's responsive utilities and how to apply them effectively in a real-world project.

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

Responsive Design Refinement: I'm looking to further optimize the responsiveness of the dashboard. Although it adapts well across breakpoints, I'd like suggestions on any potential tweaks or best practices to ensure consistency and optimal spacing on unusual screen sizes.

Component Abstraction & Reusability: I want to ensure that my components (like UserProfile, ActivityCard, and ActivityGrid) are as reusable and maintainable as possible. Any insights on abstraction, code splitting, or better state management would be very helpful.

Performance Optimization: Since the layout involves dynamic image rendering and responsive adjustments, I'm curious about techniques or tools that could help with performance improvements, especially for mobile devices.

Enhanced Interactivity & User Experience: While the basic interactions work fine, I'm looking for ideas on how to introduce more advanced animations or transitions that could make the dashboard feel even more engaging.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mustapha's solution.

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.