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

Responsive Landing Page using CSS Grid revised

Reni•40
@renikoulen
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


I struggled with using fonts locally for a good part of the exercise. Also, I am unsure why I could not create a border-radius around the cards. Why can't I position the cards wrapped inside a <main> section to the center of the page? And why does the button move and partially cover the paragraph text when the screen gets smaller?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Manish Patel•740
    @savvystrider
    Posted over 2 years ago

    Hi, I'm glad you didn't give up! I think it came out well.

    If you want to apply specific styles when the screen is below a certain size, you'll need to use Media Queries. The syntax takes some getting used to, but it would go something like this:

    @media (max-width: 375px) { /* … */ }

    Quick notes:

    • remove max-width: 85rem; from the body element. It will center the content a little more smoothly.
    • there's a small typo in your footer styles that's causing some weird formatting: width: 100dvh;
  • Reni•40
    @renikoulen
    Posted over 2 years ago

    Hi @savvystrider. I am still working in a solution based in your Feedback. I think I am getting there. Thanks a lot for these helpful hints.

  • Manish Patel•740
    @savvystrider
    Posted over 2 years ago

    Looks good! Try to get the content horizontally and vertically centered on the page. You can use grid or flexbox to achieve this.

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

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