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

Responsive Bento Grid using HTML and CSS

accessibility, lighthouse
Rebecca Padgett•2,100
@bccpadge
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?

All feedback is welcome and greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•7,050
    @MarziaJalili
    Posted 5 months ago

    You have done a great job, Girl!!!

    One thing though 🤔

    Wouldn't be better if the hover state were a bit smoother?

    You can apply this line of code to the elements:

    transition: border-color .2s;
    

    I also recommend setting a media for the tablate. Using grid-template-areas it won't be that challenging.

    Other than these your solution is AWESOME!!!

    Marked as helpful
  • Yacoub AlDweik•3,090
    @YacoubDweik
    Posted 5 months ago

    Hey!

    Good job!

    I really liked how semantic your HTML is! brilliant! the structure is amazing!

    there's only one thing that makes your app overflow in mobiles, this one: <ul class="social__list"> give that flex their flex-wrap: wrap and everything is gonna be good! keep it up!

    Something I forgot to say is that using h1 and manipulate that by hide it or move it away is not recommended! sometimes the search engines detect that and this will impact the rank of your page.

    Marked as helpful
  • MEHNOOR SHAHBAZ•720
    @Mahnoor366880
    Posted 3 months ago

    your design is so amazing your hard work pay off keep it up

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.

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

Oops! 😬

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

Log in with GitHub