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

3-column-preview-card with React and Tailwind

react, tailwind-css
Achinthya Dulshan•320
@AchinthyaDulshan
A solution to the 3-column preview card component 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?

That time I used React with props and it is easy when using components. Next time I use props when it is necessary. Also that time I added more configurations on tailwind and it is easy when we work with our own project.

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

When I passing the props firstly I create all props as array and passed values to that all props in map. that is descriptive but it is add more repetitive codes then I pass card object as a prop and access values in card component. when dealing with 3-card component we need to add rounded borders, 3 cards are child elements then I used overflow-hidden to get the rounded borders. In hover effect in buttons I used bg-transparent when hover rather that adding color on hover

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

when I tried to change background color of buttons in hover using custom colors which are defined in tailwind.config.js it doesn't work.

Any other suggestions regarding my solution are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 12 months ago

    Hi again,

    Nice project! It looks good on all devices and is fully responsive. One minor improvement would be to add a breakpoint for 650px and cap the text width to 50% so it doesn’t get too wide on tablets and small laptops. It’s also a good practice to add custom Tailwind breakpoints using the config file.

    I checked your color configuration, and it seems fine to me. If you’re experiencing issues, it might be a CSS specificity problem. A workaround would be to add an ID with regular CSS, like #button:hover { /* logic here */ }, because this would override the Tailwind classes if hover:text-colorname isn’t working for you when applied dynamically.

    Otherwise, nice job using a modular React approach!

    Hope this was helpful.

    Best, Teodor

    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