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

Bento Grid Main project using CSS Grid

Nnaemeka Daniel John•20
@dukeofhazardz
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 super proud of how the Bento grid project turned out, especially getting a clean, responsive layout that flows well on all devices thanks to CSS Grid and Flexbox. It was satisfying to see everything snap into place as I tweaked it. Next time, I'd probably play around with some smooth animations to make it feel even more interactive and take a closer look at accessibility tweaks, like boosting color contrast and adding screen reader support. I’d also use CSS variables to make it easier to fine-tune the styles down the line.

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

The biggest challenge was nailing down the grid layout, especially getting the items to align exactly as I wanted across different screen sizes. I hit a few roadblocks with elements shifting out of place, but using CSS Grid’s grid-template-areas saved the day by giving me precise control over each section. Debugging the layout was a bit of trial and error, but Chrome DevTools became my best friend for checking spacing and alignment. Adjusting the media queries and testing on various devices really helped make everything consistent.

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

I’d love feedback on making the grid more responsive, especially around tablet-sized screens. I noticed that some elements don’t align perfectly when the screen width falls between desktop and mobile breakpoints, and I’d appreciate any tips on refining the layout for that range. Additionally, if anyone has advice on optimizing load times with images or handling font scaling across different devices, I’d be interested in ways to make the experience smoother without sacrificing design.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Nnaemeka Daniel John'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
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.