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

Responsive 4 Card Feature Section Using CSS Flexbox

Anosha Ahmed•9,300
@anoshaahmed
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Would appreciate any suggestions to improve my code!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • PhoenixDev22•16,850
    @PhoenixDev22
    Posted over 3 years ago

    Well done Anosha Ahmed ! I checked your solution . Your solution is great Keep up !

    Marked as helpful
  • noor•540
    @Maahnoor
    Posted over 3 years ago

    hi, great solution, perfectly matches the design. Looking at your code it seems you designed the website for mobile and then added media queries for larger screen sizes. is there an advantage to this? I am new to web development and have been doing it the other way around. will appreciate an explanation :)

    Marked as helpful
  • Harshdeep Singh•220
    @JrDevHarsh
    Posted over 3 years ago

    The design of your solution is so much accurate that it matched the given challenge. You did a nice job.

    Marked as helpful
  • Alex•660
    @al3xback
    Posted over 3 years ago

    Hi Anosha,

    I think this structure is not well optimized when have long content. (https://prnt.sc/24lvdv1, https://prnt.sc/24lvvu0)

    Marked as helpful
  • Fernando FeN•425
    @Fernando0654
    Posted over 3 years ago

    I think it's because of the h2 element, before h1. You have h1, h2 and h3 but they are not in a sequentially-descending order

    Great work, btw. Love when fits so well in the design / solution window

    Marked as helpful
  • Moayad•100
    @Moayad7
    Posted over 3 years ago

    great work!

  • Adarsh Rai•560
    @AdarshRai0
    Posted almost 3 years ago

    Well done Anosha Ahmed ! I checked your solution just wanted to know how you make your solution exactly same as the design any tips it can help me to improve;✨🎯

  • Anosha Ahmed•9,300
    @anoshaahmed
    Posted over 3 years ago

    Well, I have h1, h2 and h3 in my code so i don't know about the accessibility issue. I guess i should have had them in ascending order.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

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

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