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

Tailwind CSS Time Tracking Dashboard

tailwind-css
Rebeka•170
@BekiaD
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 layout and the animations. Little details like hover states.

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

The refactoring of the JS into for loops was a bit mind boggling. I find it difficult to think through the process so I use mindmaps for this. Deploying the tailwind project to netlify also took quite some time to figure out

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

Any feedback is welcome.

  • on mobile view the top part of the card is cut off because of the h-screen, but if i change it to sm:h-screen it looks fine on mobile, but not aligned on desktop view
  • There is a part commented out in my code that would pop up a share button when hovered over the ellipses (...) at each card. I found here difficult to work with the cards individually with a lot of repetition.
  • Also the bigger issue is that after the mouseover event the popup stays there.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dipesh•430
    @Dipesh-sapkota1
    Posted 10 months ago

    🎉Congratulation on completion of your project🎉

    1.Card Overflow and Layout: -To prevent card overflow issues, consider using min-h-screen. Browsers naturally try to preserve content, and issues often arise from unnecessary CSS. Your layout breaks at the small break-point because the required columns were not specified to fit all the cards. Ensure that your grid system accommodates all elements at different breakpoints.

    2.Netlify Deployment: -Great job attempting to deploy on Netlify! However, I couldn't view your website. When deploying with frameworks or libraries, make sure to specify the base directory and build command. This extra step is crucial for successful deployment.

    3.JavaScript Improvements: -Your JavaScript is currently not working. Here are a few suggestions: Use querySelectorAll for selecting multiple elements and adding event listeners. Break down large functions into smaller, reusable, and manageable functions.

    4.Design Focus: -Being creative is fantastic, but make sure to focus on basic design principles first. This will ensure a solid foundation before adding more creative elements.

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