Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Time tracking dashboard (Next.js + TypeScript + Tailwind CSS + ESLint)

accessibility, next, tailwind-css, typescript, pwa
Melvin Aguilar 🧑🏻‍💻•61,020
@MelvinAguilar
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there 👋, I’m Melvin, and this is my solution for this challenge. 🚀

🎁 Features:

  • Tabbed interfaces. 📑
  • Controllable using arrow keys and Tab. ⌨️
  • Tooltip that allows copying statistics. 📊
  • Resemblance with the original design. 🎨
  • Progressive Web App (PWA) support. 📱🌐
  • Small animations with Framer motion. 🎬
  • No errors or warnings using ESLint (Airbnb style guide). ✔️
  • Client-side fetching with SWR to simulate an API. 🌐
  • Custom hooks. 🎣
  • Tested with the TalkBack screen reader on mobile. 📱

🛠️ Built With:

  • Nextjs 13.5.4. ⚛️
  • TypeScript. 📝
  • TailwindCSS. 🎨
  • Framer-motion. 🎬
  • ESLint (Airbnb style guide). 📦

❓ Question:

Not very proud of the prop drilling in the solution. Any recommendations to avoid it? I've tried using the Context API to reduce it, but I don't see much difference.

Any suggestions on how I can improve and reduce unnecessary code are welcome!

Thank you. 😊✌️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • saidi ali•270
    @alihydro
    Posted over 1 year ago

    Excellent solution. Really impressive 👏👏.

  • Mohammed Fakih•1,590
    @javascriptor1
    Posted over 1 year ago

    Hi MELVIN ,

    Excellent solution. Really impressive 👏👏.

    The only issue I noticed is the background color for the 6 main cards is visible on the bottom corners (right & left).

    Take for example the work card. If you notice the bottom corners from right and left, you will see orange colors from the background. It's very slight though, merely noticed by eyes.

    Your solution is perfect indeed. I hope if you have free time to share with us in a writeup how you can produce an exact pixel-perfect solution in such a remarkable way.

    Thank you so much.

  • Yousef•90
    @ousey-ousey
    Posted over 1 year ago

    THAT'S GOOD i noticed that the bottom of number appear last-week and result bur while i use daily or monthly still the word "last week "

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

Oops! 😬

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

Log in with GitHub