Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 6 months ago

Responsive page using CSS Grid and Flexbox

FranciscoDavidCampuzanoMelgarejo•130
@FranciscoDavidCampuzanoMelgarejo
A solution to the Four card feature section 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?

I think the page is looking good and responsive. Just a few lines of HTML and CSS. I am proud of doing it in just a few hours. Next time, maybe I'll try to use areas for CSS Grid, but I just thought that they were not necessary this for this project.

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

The main problem was changing the order of the cards for desktop design. I just followed a mobile first design, so this part was easy. The desktop design was a bit tricky, but not very difficult. So, overall it wasnt' as harda as I thougth.

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

I would say the shadows were not enough good if they are compared with the design, so a bit of help in how to make the shadows perfect according with the design.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Carl•1,235
    @CarlHumm
    Posted 6 months ago

    Hi there

    Good job on the solution. It can be very tricky to eyeball shadows and get the perfect value. I think you've done well with your solution, it responds well. From a glance it looks like the design shadow has a wider spread, is more offcenter and a different hue.

    Much easier to guess when you have a design file to work from :)

    box-shadow: 0 15px 30px -11px rgba(131, 166, 210, 0.5);
    

    You may also want to give your cards a white background to help them stand apart from the neutral gray background.

    Hope this helps and good luck with future challenges!

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