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

Desktop version with CSS grid

Zarak•100
@zarak
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 used CSS grid for the first time in this project. It definitely made the layout really convenient. The mobile version also becomes a piece of cake thanks to CSS grid.

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

The biggest challenge was trying to get the top border trim colour to look like what's in the mockup. Initially I used a border, with a solid line. But the problem is that if I set the border thickness to anything less than the border-radius, the border would sort of curve down at the edges. I solved this by using a ::before pseudo-element. I haven't yet had many opportunities to use these pseudo-elements but I can appreciate the power they offer a little more now.

I still struggled a bit because I had to tweak a few settings on both the card class and the card::before class, such as overflow. But eventually I found something that works.

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

I tried using REM for this project instead of pixels. I used a margin top for the spacing between the header and the top of the viewport. I also used a margin top for the cards wrapper. I'm not sure if there is a better way.

One improvement I should make is to use variables for the colors and spacing.

I need more practice with the BEM naming convention.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • emiwoo•80
    @emiwoo
    Posted 6 months ago

    Wow, this looks better than mine. I should've scaled my cards up too when in desktop version

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