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

Four Card Feature Section - Built with React and Tailwind CSS

react, tailwind-css
P
tasosbeast•150
@tasosbeast
A solution to the Four card feature section 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?

What I am most proud of

I am proud of starting to learn React and successfully applying it to this project. It has been a great learning experience, and I am happy with how I managed to create interactive components and manage state effectively.

What I would do differently next time

Next time, I will try to make the project simpler and not overcomplicate things. While using React for this project was a valuable learning experience, I will consider the scale and complexity of the project before deciding on the tools and technologies to use. This approach will help me focus on the core requirements and deliver more efficient solutions.

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

Challenges I encountered

At some point, the project kind of overwhelmed me, and I felt like I was spending too much time on it. The complexity of managing state and ensuring all components interacted correctly in React was a bit challenging. However, I overcame these challenges by breaking down the tasks into smaller, manageable pieces and focusing on one issue at a time. I also relied on resources like the React documentation and interactive tutorials on Scrimba to help me understand and implement the necessary concepts. This approach helped me stay organized and gradually complete the project.

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

Areas where I would like help

  • State Management: I would appreciate feedback on how I managed state in this project. Are there more efficient ways to handle state for this type of application?
  • Component Structure: I would like input on the structure of my components. Are there any best practices I should follow to make my components more reusable and maintainable?
  • Performance Optimization: Any tips on optimizing the performance of my React application would be helpful. Are there specific techniques I should consider for improving load times and responsiveness?
  • Styling with Tailwind CSS: Feedback on my use of Tailwind CSS for styling would be great. Are there any improvements I can make to my class structure or usage of utility classes?

Thank you in advance for any feedback and suggestions!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yonerfy•210
    @Yonerfy
    Posted 5 months ago

    Very good work, I liked the effect you added to the cards.

    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

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub