Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Basic HTML and CSS 3

Óscar Rabadán Martínez•150
@Oscarandio
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


Hello! The desktop version looks amazing. I dare to say it looks exactly the same as the preview, but I can not say the same with the mobile version... Can someone help me to make this responsive and looking good on mobile version? I know about the mediaqueries and all that, but for some reason I can not make it work. I would appreciate some guiding here, thanks!

*Things needed on mobile version: Change the border-radius and the width of the boxes.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Babajide Peter Oyafemi•200
    @Babajide777
    Posted almost 4 years ago

    Hi Oscarandio,

    I advise you use CSS Grid to make it more responsive. CSS grid made build the project a lot easier. You can check my solution here: https://www.frontendmentor.io/solutions/semantic-html5-markup-css3-flexbox-grid-fZ4rIBPVH

  • Agata Liberska•4,075
    @AgataLiberska
    Posted almost 4 years ago

    Hi Oscar!

    In general, it's a lot easier to just start with the mobile design, since divs just stack on top of each other in a column, just like you want them to be here. So what I would do is add a media query with a min-width and only apply display: flex to the .container class on viewports wider than, say, 900px or so? You'll probably want to set a max-width on mobile and unset or change it on desktop.

    Another thing is - I would set min-height on the body element, and set it's display to flex to center the container inside the body :)

    What is tripping you up right now as well is the padding you've got set on the body - that's what is causing the last card to be below the other two on the preview above.

    And to sort the border-radius on the cards - you can set that on the container as well, just make sure to add overflow:hidden so that the corners of individual cards don't cover the rounded container corners.

    Hope this helps, let me know if you have any questions!

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