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

Simple 3 column card using basic HTML and CSS

Lê Hoàng Long•290
@JamesWallison1
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?

It was finished easily :)

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

No challenges I think

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

Nope, I don't really but if you can't, please feel free to give any solutions!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 1 year ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have a suggestion regarding your code that I believe will be of great interest to you.

    CSS 🎨:

    • The button elements needs to have a hover state with transparent background, actually we can handle that issue with a css color function named rgba()

    • The rgba() function define colors using the Red-green-blue-alpha (RGBA) model. RGBA color values are an extension of RGB color values with an alpha channel, which helps us to take control over the opacity of the color.

    • So just add rgba(0,0,0,0) for the button elements during hover

    • Let's look an example
    button:hover {
      background: rgba(0,0,0,0);
      color: white;
      outline: 1px solid white;
      transform: scale(1.02);
    }
    

    • Additionally, I want to address the duplication of rules which you've been applied for button elements. Currently this is your rules for them,
    .button-1{
        padding: 12px 30px 12px 30px;
        border-radius: 20px;
        border: none;
        background-color: white;
        color: var(--Bright-orange);
        font-family: "Lexend Deca";
        font-weight: 500;
        cursor: pointer;
        transition: all 0.2s ease-in-out;
        justify-content: flex-end;
        margin-top: 60px;
    }
    
    .button-2{
        padding: 12px 30px 12px 30px;
        border-radius: 20px;
        ....      // Same rules
    }
    
    .button-3{
        padding: 12px 30px 12px 30px;
        border-radius: 20px;
        .....    // Same rules
    }
    

    • We don't need this much of duplication in our code, this will result in poor result when it comes to web performance!

    • Here's the refactored style rules
    button {
        padding: 12px 30px 12px 30px;
        border-radius: 20px;
        border: none;
        background: white;
        font-family: "Lexend Deca";
        font-weight: 500;
        cursor: pointer;
        transition: all 0.2s ease-in-out;
        justify-content: flex-end;
        margin-top: 60px;
    }
    
    .button-1 {
       color: var(--Bright-orange);
    }
    .button-2 {
       color: var(--Dark-cyan);
    }
    .button-3 {
       color: var(--Very--dark-cyan);
    }
    

    • In the above rules, we selected all button elements to apply general button styles and then we added the classes you've added in markup for modifying like button-1, button-2 and so on to apply unique colors for each of them without duplicating entire styles.

    • Now you have gotten the desired result for hovering without hassling in an efficient way.

    • Pro tip: you can use transparent value for background property to get the same effect as rgba(0,0,0,0) but using rgba provides more granular control over the color correction.

    • If you have any questions or need further clarification, you can always check out my submission for this challenge where i used this technique and feel free to reach out to me.

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

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