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

Mobile first with React.js, Framer Motion and Tailwind CSS

accessibility, framer-motion, react, tailwind-css, vite
Karol Binkowski•1,620
@GrzywN
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first project in React and I've learned a lot 😇 The components may be too big and the code is not as clean as it could be, but I'm really happy with the final result, especially the animations. For the first time I used some other tools like Tailwind or Framer Motion and it was a pleasure. Any feedback is welcome here 😁.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted almost 3 years ago

    Hi, Karol Binkowski! 👋

    Good job on this challenge! 👏 Your solution looks great and responds nicely! 🙌 I really like the animations that you added to the components, as well! 😀

    A tiny suggestion I have is to wrap the meatballs menu icons in button tags since they would typically open some sort of menu when clicked.

    I took a look at your code and noticed that you were doing this in your components:

    export default function Component(props) {
      const { prop1 } = props;
      const { prop2 } = props;
      const { prop3 } = props;
    
      // etc.
    

    It's much easier (and nicer-looking, haha) to simply grab those props using object destructuring syntax, as in:

    export default function Component({ prop1, prop2, prop3 }) {
      // etc.
    

    You can then reference those props normally in the rest of your function. If you'd like to learn more about object destructuring/assignment, check out this helpful video on the topic.

    Hope this helps. 😊

    Keep coding (and happy coding, too)! 😁

    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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub