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

👻 Grid Section: Bento (HTML + CSS + JS)

animation
Natali 👻 Grimm•1,190
@Grimm-N
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 excited to start the Junior stage. I've tweaked the color scheme a bit again, added some animation, and transition states for the Grid layout.

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

I would really like to make this grid more flexible and responsive, rather than just changing its state with media queries, but for now, this is what we have.

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

I would love to hear suggestions on how to make the grid more flexible.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Asilcan Toper•2,960
    @KapteynUniverse
    Posted 8 months ago

    Hey Natali, great job.

    I don't know how you can implement to a grid something like this where every item should have a specific position and span but you can combine auto-fit, repeat and minmax for a responsive grid.

    grid-template-columns: repeat(auto-fit, minmax(256px, 1fr))

    With this method, items wrap with an ugly way tho. If you try it, Kevin Powell has a nice video for that problem.

    Also i think this one fit nice with your page.

    body {
        overflow-x: hidden;
    }
    
    body::-webkit-scrollbar {
      width: 0.25rem;
    }
    
    body::-webkit-scrollbar-track {
      background: #1e1e24;
    }
    body::-webkit-scrollbar-thumb {
      background: #6649b8;
    }
    

    Look to the scrollbar

    Marked as helpful
  • Gotyan•390
    @eduardoramirezrojas
    Posted 8 months ago

    This is a different level! 😲😳 I loved the background, it looks like it has a filter on it which makes it look even more interesting. The overall design is very well taken care of, it looks polished and visually appealing. However, I noticed that you are using a lot of div, you might consider using more semantic tags to improve the accessibility and SEO of your project.

    Other than that, it looks beautiful! 😊 I would love to get your feedback on my projects too; your perspective would be a great help in continuing to grow.

    Thanks and great work! 🙌!

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