Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

4 Card feature section - HTML, SCSS, Grid, @keyframes & mobile-first!

bem, sass/scss
darryncodes•6,350
@darryncodes
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone 👋

Well well well ... mobile-first!

I think this is a turning point for me, i finally embraced the dark-side. And what can i say, it's liberating. My code feels cleaner, simpler and more legible. It might be due to the design but i'm definitely converted 👀

I took the time at the start of the project to really understand how to work with min-width instead of max-width and it paid off. I also got a bit unnecessarily carried away with @keyframe animations at the end and changing them up per breakpoint 😂

Anyway, your feedback would be greatly appreciated!

Happy coding 🤙

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tiass•295
    @Tiasstiass
    Posted almost 4 years ago

    Good job! 👏

    Tested it on Safari iOS, looks neat! Few feedbacks:

    • Regarding the colored top border: You could make it a div or the best solution I think, is to use a ::before pseudo element,
    • Setting fixed heights is not considered good practice, the content should define the height of an element, be it the padding etc..,
    • Any reason behind the font-size: 50%, 62.5% makes sense but why 50%?
    • @import is being depreciated and Sass team is discouraging us to use it, look into @use and @forward,
    • You are using scss syntax not sass, consider renaming your folder.

    Excellent job overall, keep up the good work 💪

    Marked as helpful
  • Harmanjot Singh•985
    @arkharman12
    Posted almost 4 years ago

    Looks good! But why not import the <svg>s in <img> tags? Instead of putting them in the markup and then linking them.

  • darryncodes•6,350
    @darryncodes
    Posted almost 4 years ago

    Thanks for the nudge in the right direction @mattstuddert 🎉

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub