Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

3-column preview card component | React | CSS | Add some modification

react
Jeje•2,050
@AkoToSiJeromeEh
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


Hi guys, I just want to share that I have accomplished the 3-column preview card component. So far, so good! It has been enjoyable and fun to work on, especially because I made some modifications to the background colors, hover effects, and animations. That's all! Happy coding, everyone, and mabuhay!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted about 2 years ago

    Heyo,

    It's really nice to see a unique take on the challenge, well done :) That being said, I'd make a few suggestions where you could perhaps improve.

    I'd remove the opacity animation from the card background, it's not super pleasant for the eyes to see that flickering from opacity 0. Also the background doesn't return to it's original state even after you click on the "Hide Spec" option (the image stays). Maybe it's how it's intended to work, its just not what I was expecting.

    There's also a small issue with the responsiveness, if you check your solution around 800px, it has an overflow. Maybe you need to adjust the breakpoint a bit to fix this.

    Few words about React best practices:

    Usually folders are written lowercase (components, pages, styles, etc). Also, usually each component and page has its own folder. So for example, let's say you want to make a button component. This would live inside a "components" folder, and inside that, there would be a "button" folder with Button.jsx.

    In a somewhat larger project it's also nice idea to use something like Sass, so you could include specific styles for each component. Like, in the above mentioned button folder, there could be a Button.scss file as well, with the unique styles belonging to Button.jsx. Apart from unique styles, you can obviously have a styles folder that contains general styles (typography, variables, etc).

    There is no need to do this:

    import React from "react";
    
    const [hoverCar, setHoverCar] = React.useState(false);
    

    You should instead do specific named imports:

    import { useState } from from 'react';
    
    const [hoverCar, setHoverCar] = useState(false);
    

    This isn't so React-specific, but I thought its worth mentioning it: conventionally, classnames should be lowercase too. For example, "Card-Wrapper" should be just "card-wrapper".

    Apart from these, I think you did a good job and it's nice to see you put so much effort in it. Keep up the good work ^^

    Marked as helpful
  • Christian Patrick Nebab•1,080
    @Dng120696
    Posted about 2 years ago

    when a designer become a web developer :) haha nice style and animation man ,hope soon im gonna learn react too . but now im still focusing JS

  • yssachi•0
    @yssachi
    Posted about 2 years ago

    Great Work!👏 probably this is one of my favorite works that you've done, I really love the changes/modifications you made here✨, as I always said keep striving to achieve your dreams love love

  • Momin Riyadh•370
    @momin-riyadh
    Posted almost 2 years ago

    It could be better in terms of transition and animation smoothness! You should focus on scrimba courses and practice more and follow other developer code

    Moreover, you need to subscribe, and to get started, follow this link. It'll take you to the course's website, where you can sign up and start your JavaScript learning journey. Don't worry; the beginner-friendly system is designed to help you grasp the fundamentals.

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 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

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

Oops! 😬

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

Log in with GitHub