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

Grid layout section - Line-based placement

bem
Mohammad-Moneer•120
@Mohammad-Moneer
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’m most proud of the practical experience I gained with the CSS Grid layout, especially using line-based placement techniques to create a responsive design. This project also marks my first experience with the BEM naming convention, which helped me organize CSS classes more effectively. as for what I would do differently next time: I’d focus on further optimizing my CSS by grouping common styles and potentially using CSS custom properties more extensively.

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

Adjusting the layout to fit various screen sizes with multiple media queries was a bit challenging. I aimed to maintain the core layout structure (with one tool on the left, one on the right, and two stacked vertically in the center) while ensuring each tool's size remained suitable for its content. To achieve this, I used a CSS Grid layout with three equal columns and adjusted the width of the tools container for different screen sizes. For large screens (above 1110px), I set the container width to 1090px. For screens up to 1110px, I made the container span nearly the full screen width, allowing for horizontal margins. On smaller screens (up to 800px), I switched to a single-column layout and set the container width to 350px or maximum 90%. Through practical experimentation, I achieved a balanced, responsive design that keeps the layout stable and content visually accessible across screen sizes.

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

I need to know if there is an alternative responsive layout approach that could be used?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mohammad-Moneer's solution.

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.