Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Vue3, Pug, Sass, Typescript, Vite - Time tracking dashboard page

Faris P•2,810
@FarisPalayi
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I know the tab switching state change and tablet version of the site is kinda odd, but I figured if I don't publish this now, I would try to make it "perfect" and in the end what will happen is that after a lot of days the only thing that'll change would be some pixel values and some other tiny unimportant stuff.

  • This was my first time using an experimental feature of Vue, the ref sugar. Which is, if you know the Composition API in Vue, it helps us use the ref like reactive. i.e. the .value can be omitted by changing ref into $ref and additionally, it doesn't need to be imported.

  • I learned the trade-offs of using experimental features because a lot of the time the site deployment failed because of some package's patch or version updated.

  • Instead of using the Composition API setup function in the script, I used script setup which will drastically reduce the boilerplate code and gives clear distinction between Options api and Composition api code.

  • One additional thing I added is, the tab's active state will be stored in localStorage. So, even after refresh, it'll have the same active state. Also, I tried to make it responsive to smaller devices.

  • Most of the time when I use Vue cli, my laptop gets laggy, but since I used Vite to scaffold the project, it was a smoother and 'non-laggy' experience. I'll certainly use it in the future projects.

  • Things I've learned while doing this challenge are in the README.md btw.

I'd love to hear your feedbacks and criticisms on my take 😀

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 Faris P'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.