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

Responsive landing page using CSS Flex

pure-css
keftajnr•240
@keftajnr
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 am really proud of how i pushed myself with this project. It was my first time working with CSS Flexbox properties like flex-direction, gap, and learning how to use them effectively made a big difference in my layout. I also explored using multiple media queries to make the site responsive, which was a first for me and something i am excited to build on. Compared to my past projects, this one felt like a much bigger challenge, but it helped me grow and learn much more.

Looking back on how i did, i would focus on writing more efficient and cleaner CSS. i would avoid using fixed widths and heights and rely on more flexible units for responsiveness. I would also like to improve my speed and workflow and being more intentional with layout decisions.

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

Firstly, I had issues with the responsiveness of the site. I initially made use of fixed widths and heights which hindered the smooth flow of the site when resizing, thankfully, i got to use multiple media queries at different max widths which made the site run and resize smoothly.

I also had issues with CSS flexbox elements, although it was not too worrisome, i still got ahead of it after continuous trial with new flexbox properties i got to know about and make use of.

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

Definitely, i would need help with the accurate positions of the elements as in the design image.

Also, i would require assistance with the responsiveness of the site to ensure it resizes with ease.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Afeliciosilva•100
    @Afeliciosilva
    Posted about 2 months ago

    Muito bom seu código

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