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

Four card feature section, HTML, CSS

cxkeeley•50
@cxkeeley
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback is very welcome, I've learned some solutions from PhoenixDev22, such a great mentor to follow, waiting for your comment bro, cheers, and happy coding

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aymin•180
    @ayminahmedpk
    Posted over 3 years ago

    Looks decent. However, there's a few ways you can raise your game.

    I noticed there is an animation when moving from mobile to 'laptop layout', but not when moving to the desktop layout. Consistency is actually a big part of UX. Try to have the animation in both cases or in neither case, because it's jarring when it only happens on some occasions. But if you're just experimenting, then congrats, it works and looks ok.

    There's a few other things you could do too. You can make the design more accurate by using PerfectPixel extension on Chrome to fine tune your style, and you can use Figma to map out the image so you know the exact fonts and box sizes.

    Also, consider using Grid, that way you can get rid of the 3 'left', 'middle' and 'right' divs. It'll help you simplify your markup as well as your CSS.

    Finally, if you're going to restart and resubmit this challenge, look into BEM as well.

    If you look at my profile, I have submitted this challenge with a Figma file (my own, not from FEM), so you can get it from my repository and use that as an example. Also, I've made a previous comment for this same project explaining all of this in more detail, so that might help you out too.

    BTW, I did this challenge twice. My first submission was with Flex, and the second one was with Grid, so if you want to compare the code you can check my commit history for that repo.

    Marked as helpful
  • cxkeeley•50
    @cxkeeley
    Posted over 3 years ago

    wow, I already saw yours, and your solution is almost 100% perfect, great job, I'm still learning about SCSS and BEM, I will follow your advice. thanks

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