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

Time-tracking Dashboard using Tailwind CSS, jQuery & JS

tailwind-css, jquery
Mehrine•230
@YarAllyMehrine
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?

The first time i actually use Tailwind CSS since i have learnt it. It is much more complicated than expected due to the new version.

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

The jQuery facilitates the DOM Manipulation but it cannot be used every time especially in JavaScript function.

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

I need help to understand why I couldn't use Tailwind CSS theme and other utilities. I had to use CSS alongside Tailwind CSS (:root instead of @theme). Also, I couldn't get the Desktop layout well, try multiple approach. There is a possibility that there is an existing CSS that is creating a side-effect to prevent the layout to turn out as expected, but i need help on that. Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vladimir Gatara•440
    @vgarmy
    Posted 4 months ago

    The learning experience with Tailwind has been enjoyable, but at times it also presented difficulties in achieving the desired responsiveness. That said, I find the design overall to be very good and the layout clean and effective.

    I would start with setting a width for the section so it dosent span over the screen,

    Marked as helpful

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