Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

3-column preview card responsive UI

Vigneshwaraa•220
@Vicgok
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


Does it look good? Any tips and tricks for responsive UI with less code?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ben•770
    @BenConfig
    Posted over 3 years ago

    This looks pretty good. I would perhaps try to simplify the HTML as there seem to be some unnecessary elements.

    Maybe something like this:

    <main>
        /* Card 1 */
        <section>
            <h2></h2>
            <p></p>
            <a></a>
        </section>
    
        /* Card 2 */
        <section>
            <h2></h2>
            <p></p>
            <a></a>
        </section>
    
        /* Card 3 */
        <section>
            <h2></h2>
            <p></p>
            <a></a>
        </section>
    </main>
    

    And the images are just for decoration so they can be added using a ::before pseudo-element on each <section>, instead of an HTML element.

    Marked as helpful
  • Alex•2,010
    @AlexKMarshall
    Posted over 3 years ago

    Hey there, this looks pretty good. It's responsive and doesn't overflow, which is great.

    The HTML is a bit off. You've got a <section class="main">. Just make that a <main>. You need one anyway, and <section> doesn't have any semantic meaning unless it's labelled with aria.

    You've got three <h1> elements. You can only have one of them on the page. That means you'll need to have a hidden page title in an <h1> somewhere, and make the car headings <h2>

    At some screen-sizes the headings get mis-aligned. I'd probably move the headings up into the <header> wrapper and that should make it easier to keep them lined up.

    It's cool that you're experimenting with fluid typography using clamp. It can be a really useful tool. However, for my tastes in this layout it's making things less readable. Generally it's a really useful technique for heading text, less useful for body text. Here I would say your small size of 0.9rem is too small. Body copy shouldn't really go below 1rem. And on big screens 1.94rem just looks too big. Also, having a fluid line-height doesn't make sense here. It will scale with the size of text anyway, so just leave it at 1.5 or 1.25. I think the paragraph text in general would look better at a fixed font-size of 1.25rem.

    I think you could do this with fewer media queries too. You only really need one, which changes the flex-direction of the wrapper from column to row once you get above your breakpoint.

    Marked as helpful
  • Vigneshwaraa•220
    @Vicgok
    Posted over 3 years ago

    This is so helpful and for the svg I'll try the pseudo method on my next challenge.. Thank you.

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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