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

Four Card Feature Section with HTML & Sass

Tinymoly•160
@TinymolyDD
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 Flexbox layout mode to finish this project. By combining an outer Flexbox for horizontal layout and inner Flexboxes for vertical content, I achieved a structure similar to Grid. In my next project, I'll try to explore Grid instead.

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

One challenge I encountered was when trying to add colorful borders to the top of the cards while maintaining the cards' rounded corners. Initially, I used the border-top property. However, the border followed the curve of the card’s border-radius, which wasn’t the effect I wanted. To overcome this, I added a custom div directly to each card and applied different colors. This approach ensured the border remained straight and sharp, without being affected by the card’s border-radius. Additionally, by using overflow: hidden, I made sure that any part of the border extending beyond the card's edges was hidden, preserving the desired sharp edge.

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

For the card borders, if you have different solution, welcome to discuss! Also, I would appreciate any feedback or suggestions regarding my code. If you have any recommendations for improvement, I’d be happy to hear them.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Carlos Castillo•520
    @CharlieCastleWeb
    Posted 5 months ago

    Hi! Awesome solution.

    To solve the border problem I would suggest using a :before element so you don't need to add an extra empty div.

    I really liked your SCSS, only thing I'd say about is maybe separate it in multiple smaller files for improved organisation.

    Anyway, good job! Keep up the good work

    Marked as helpful

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