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

Binto Grid Card

accessibility
NayyabAqib•650
@nayyabaqib
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 used HTML, CSS, and a bit of JavaScript to complete this challenge. 🔹 CSS Grid Layout was used to create a responsive and well-structured Bento Grid UI. 🔹 I also utilized Flexbox to properly align the content (text, buttons, and images) inside each box. 🔹 Images and styling were adjusted to match the original design preview as closely as possible.

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

🔹 Adjusting image sizes and placement was the most challenging part because the original design had specific scaling and proportions for each image. 🔹 I had to experiment with grid-template-columns, flexbox, max-width, height, and object-fit to make the images look well-balanced. 🔹 Ensuring that the font sizes and button placements matched the original design was also tricky.

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

✅ I improved my CSS Grid skills, especially for responsive design. ✅ I learned how to scale and center images properly so that they match the reference design. ✅ In future projects, I will use CSS Variables and Utility Classes to make my code more reusable and maintainable. ✅ I will focus more on accessibility and ARIA attributes to make the UI more user-friendly and inclusive.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chamu•13,860
    @ChamuMutezva
    Posted 5 months ago

    Hi nayyabaqib

    I see that you are enjoying the challenges lately. Please take time to read the feedback that have been posted in the earlier challenges. They are basic things that you need to fix before moving on with other challenges. The same mistakes are being repeated in most if not all the challenges. To just name a few , here are some of them.

    • not following best practices. The CSS should have its own file and then imported into the HTML FILE.
    • missing landmark elements
    • alt values that are not beneficial to assistive technology, maybe the image is decorative and then the alt value can be blank.
    • unresponsive websites.

    We are here to help you learn and have an awesome learning journey

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub