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

3-column-preview-card-component-main

Dot-theduck•70
@Dot-theduck
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


feedbacks are appreciated

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eni•180
    @EnidaShehu
    Posted about 2 years ago

    Good job on your solution!

    To make the container edges round you can add the classes and CSS code below:

    .cont-1 { border-top-left-radius: 0.5rem; border-bottom-left-radius: 0.5rem; }

    .cont-3 { border-top-right-radius: 0.5rem; border-bottom-right-radius: 0.5rem; }

    I would also advice you to use rem instead of px when sizing elements. The main advantage of using rem units is their scalability and responsiveness. When you define sizes using rem, they adjust proportionally to the font size of the root element. This means that if you changes the default font size in their browser settings, all elements specified in rem will automatically adapt accordingly.

    Keep it up :)

    Marked as helpful
  • _nehal💎•6,710
    @NehalSahu8055
    Posted about 2 years ago

    Also

    • Your cards are not centered on the screen.
    • To center card on the page.
    1. USING FLEXBOX
    body{
    min-height: 100vh;
    display: flex;
    align-items: center;
    justify-content: center;
    }
    
    1. USING GRID
    body{
    min-height: 100vh;
    display: grid;
    place-items: center;
    }
    
    Marked as helpful
  • _nehal💎•6,710
    @NehalSahu8055
    Posted about 2 years ago

    Hello Coder 👋.

    Congratulations on successfully completing the challenge! 🎉

    Few suggestions regarding design.

    ➨ Give you cards some width or more specific max-width as it will become very large on larger screens.

    ➨ Use Semantics for proper design of your code.

    <body>
    <header>
    <nav>...</nav>
    </header>
    <main>...</main>
    <footer>...</footer>
    </body>
    

    or alternatively

    <body>
    <div class="container" role="main">
    /html code goes here: 📃
    </div>
    </body>
    

    I hope you find this helpful.

    Happy coding😄

    Marked as helpful
  • Kamlesh Rajesh Yadav•5,040
    @Kamlesh0007
    Posted about 2 years ago

    Congratulations on completing the challenge! That's a great achievement, and I'm sure you put a lot of effort into it. I really liked the way you approached the challenge and the code you wrote. You demonstrated a good understanding of the concepts and applied them effectively to solve the problem.I have a few suggestions to improve your code further. The styling of button is not as per design u need to make the button transparent on hover only else the button will have the background color of the card and before hover make the background of button white not transparent

    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.

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