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

Bento Grid using CSS and HTML

Tohir564•80
@Tohir564
A solution to the Bento grid challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I could not do the grid on larger screen sizes, any feedback would really help

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Svitlana Suslenkova•5,340
    @SvitlanaSuslenkova
    Posted 9 months ago

    css for container {display: grid; grid-template-columns: 1fr 1fr 1fr 1fr;
    grid-template-rows: 1fr 1fr 1fr 1fr; gap: 1rem; aspect-ratio: 1 / 1; width, max-width...}

    .container6 {grid-row: 1 / span 2;...} ...

    Marked as helpful
  • Ilya Andreev•880
    @NeoScripter
    Posted 9 months ago

    Hey, Tohir! I'm not sure why you couldn't use grid on large screens. The way I would go about it is creating a grid layout and giving each child element grid-area property with a unique name without parethesis. For example, grid-area: emodji-group;. After that, you should give the grid container the grid-template columns and rows and simply distribute the elements inside the property grid-template-areas. You can read Mozilla docs on this topic or simply google how to use this property. Do it in a media query for a large screen. After that, it will work just fine. You can also check out Kewin Powell's Youtube channel and find a video where he explain how to do it in detail. I hope it helps!

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

Oops! 😬

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

Log in with GitHub