Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Four Card Feature Section

P
Jan Kotvaš•460
@DrakeHermit
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?

To be completely honest I am not that proud of finishing this challenge. I feel like there must be an easier way to get this to look the way that the design is set up. But I am happy that I managed to get it to look at least similar to the design.

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

The main challenge was to get the desktop part of the design look the way it should. And to be honest I am not entirely proud of how I went about making it look the way it needed to be. I created a grid of 3 columns and 3 rows wide, and I just placed the cards the way they were supposed to be placed, and I finalized it by adding transform: translateY() to the middle cards to move them to the center. It worked but I feel like there is an easier, or more efficient way.

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

I just want someone to look at my CSS and tell me if my solution to this challenge is decent.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Smaylen5•600
    @Smailen5
    Posted about 1 year ago

    Excellent solution, congratulations your css code seems well written, you made use of variables and pseudo selectors such as ::before, I liked that for the media query you used rem and not px. Is there any part of your code that gives you doubts? and still a good code 😉

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