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

Tracking Dashboard: Light Mode + Profile Switch + Tailwind + VanillaTS

tailwind-css, typescript, vite
Aakash Verma•9,500
@skyv26
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 really proud of the unique approach I took right from the start of the project. At first, it seemed time-consuming, but I trusted the process and focused on building a strong foundation.

Here’s a breakdown of what I accomplished:

  1. Design Focus: I decided to complete the design phase first, which allowed me to create a solid visual structure before diving into the technical parts. This step gave me clarity and set the tone for the rest of the project. 🎨✨
  2. Personal Touch: I modified the JSON data to include my own profile, which added a personal and unique element to the application. 🧑‍💻
  3. Light and Dark Mode: Implementing both themes was an exciting challenge! I managed to keep the images the same for both modes, and instead of toggling between images, I cleverly used CSS properties to change the image color based on the theme. 🌞🌙
  4. Clean and Lightweight: I kept things simple by using vanilla TypeScript with no external libraries for the components. This helped me maintain full control over the project’s structure and made it lighter. 💡
  5. Well-Structured Code: I created separate components and wrote clear interfaces, ensuring the code was modular, easy to maintain, and scalable. 👨‍💻🔧

Looking back, if I were to do anything differently, I would aim to plan the project’s timeline more efficiently to avoid feeling rushed during the implementation phase. Next time, I'll make sure to allocate time for both testing and refinement without compromising on quality.

Overall, I'm really happy with the outcome and excited for the next challenge!

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

One of the main challenges I faced was related to image handling in production. Since my assets were initially stored in the src folder, they weren’t loading properly when deployed. This caused issues with the images not being visible in the live version of the app. 😕📸

To resolve this, I moved the assets from the src folder to the public folder, which allowed the images to be served correctly in production. This simple adjustment solved the issue and made everything work smoothly. 💡✔️

It was a good reminder that sometimes the solution is just about placing things in the right spot! Always a learning experience! 😎

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

I'd appreciate some constructive feedback on my TypeScript code and the overall project structure. 🙏 I'm open to suggestions on how I can improve code readability, performance, or anything else that might make it more maintainable and scalable. 👩‍💻🧑‍💻

If you spot any areas where I could refine the architecture or if you have tips on best practices for TypeScript, feel free to share! 🚀 I'm all ears for valid and insightful feedback that can help me level up my skills! ✨

Important: Make sure to hover on the dashboard for a bigger screen to see the buttons for light mode and profile swap.

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 Aakash Verma'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 1st-party linked stylesheets, and styles within <style> tags.

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.