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

Solution Time tracking dashboard

tailwind-css
Stefan Bojkovski•720
@xStephx
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • TUFAIL ASHRAF•100
    @tufailashraf
    Posted 4 months ago

    @xStephx Outstanding Work Keep it Up 🙂

  • Md Mohibbullah•100
    @mohibbullah-dev
    Posted 5 months ago

    It's absolutely greate in my eyes

  • Pixel-Caje•70
    @Pixel-Caje
    Posted 5 months ago

    This is nice good job

  • Manny Verma•240
    @mverma45
    Posted 5 months ago

    looks good.

  • Md Naimur Rahman•230
    @mdnaimur
    Posted 5 months ago

    why are you not using a modern FrontEnd framework?

    your code skills are good, I suggest you optimize the code and also proper structure.

  • BRAHIM AJGAGAL•880
    @AslamtoIbrahim
    Posted 5 months ago

    Hi there @xStephx can I ask you a question ? how to use background image in tailwind css 🤔

  • nick•90
    @nicksoltaninavid
    Posted 5 months ago

    Awesome, mate! 😊

  • Donald Zarura•310
    @doniecodes
    Posted 6 months ago

    This is great hey!

  • Victoryobasi•260
    @Victoryobasi
    Posted 6 months ago

    great one, keep it up

  • Yashi Singh•670
    @Yashi-Singh-9
    Posted 6 months ago

    Hi Congrats on new challenge completion but I think fonts colors are different like for work n 32hr.

  • Sami Ul Haq•20
    @BabaKaana
    Posted 6 months ago

    The only difference I can see between your solution and design is the text colors are less bright in your solution. Increase the brightness and also increase the top border radius of every time card i.e work, play etc. Everything else looks perfect.

  • rankobinu•70
    @rankobinu
    Posted 6 months ago

    ur code looks good keep up the good work

  • Mudasir Nadeem•430
    @mudasirNadeem
    Posted 6 months ago

    very greate you are outside from Frontend mentor why?

  • Dan Carter•450
    @carter212-star
    Posted 6 months ago

    Good job. I think you should make the fonts in bold. I mean the font-family is different.

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.

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

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

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

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

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