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

Bento Grid Page Using Grid

sass/scss
Mohammad Irfan•540
@Mohammad-Irfan-Noorzada
A solution to the Bento grid 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 making the layout responsive. Next time, I'd work on optimizing the images for faster loading. I had difficulty with aligning some elements on mobile screens. I solved this by using media queries and testing different breakpoints.

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

I couldn't find what to use until I found out that grid-template-areas is the solution.

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

I’m happy with the layout on larger screens, but I’m struggling to get the mobile layout perfect. Any advice on improving the mobile responsiveness?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dominic•170
    @Dpal88
    Posted 8 months ago

    Hi @Mohammad-Irfan-Noorzada,

    Great job on completing this challenge!

    This challenge can be a little tricky, but you did a nice job on matching the desktop design!

    Your mobile layout looks good, but I see what you mean about it not quite matching the mockup images.

    My suggestion to you for future projects would be to use a mobile first layout approach, which just means to write the CSS for smaller screens first, and then use media queries for tablet & desktop devices.

    If you start using this approach I think you'll find it much easier to create your mobile layout. Also I've done this same challenge using the mobile first approach if you would like to take a look at my profile.

    I hope this helps you, and if you have any questions feel free to reach out!

    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