Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

BEM + Grid Template Areas to make responsive design a cake walk

accessibility, bem
Vikram Ingleshwar•280
@vikramvi
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • I was scared of CSS to death last year, later somehow managed to learn it and bring design to life with loads of trial and error ( just like ~ 1.25 million Indian railway employees try super hard to keep slow moving trains on track and make sure it reaches destination with 1 - 4 hours of scheduled time. I'm an Indian who stayed in Germany for many years and seen how things should be run efficiently )
  • Then I found the magic of "BEM" and "Grid Template Areas"
  • This is 1st project where I've used "Grid Template Areas"
  • I'll highly recommend to use above technique and see the difference with your other ways of styling.
  • Usage of Grid template area is like playing Jigsaw Puzzle Game where you first cut design into appropriate pieces and then place pieces in place with template area names.
  • With BEM I could play around spacing without worrying about breaking things randomly, in fact I can confidently say BEM is life saver
  • I did struggle with placement, spacing etc as it was my 1st project but this technique makes me think differently than flexbox styling, I can avoid position totally and do much lesser padding, margin etc as well

please review code and let me know areas of improvement.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 3 years ago

    Hi

    I recommend improving the html on this. There are a few foundational issues with this

    1. All those star images need to have empty alt values. These are decorative and there is already writing to communicate the 5 star ratings. Additionally, it is very frustrating for screenreader users when the same alt text is read out again and again
    2. Similarly, these should not be wrapped in figure elements. There is no point using figure at all unless you need two lots of content and one of them is a figcaption
    3. Alt text descriptions shouldn’t ever include words like “image” or “picture. The tag is already an image. If it’s an image of a named person, their name alone is fine as alt text
    4. Headings must go in order, never skipping levels and only be used for appropriate content. Eg verified purchaser is not appropriate as a heading, it’s just a paragraph
    5. Optional, this one. Consider using a blockquote for the testimonials
    6. I’m not sure you understand fully how to use sections. They act just like divs most of the time (unless labelled basically), so there is no need to use so many. Think of them as always needing a h2 heading. If you wanted to use section to wrap the 3 testimonial boxes as well as the individual boxes, really it should have an sr-only h2 like “testimonials” and then each box could keep its h3 as they belong to the section above. All this section stuff is not actually problem - like I said they are acting exactly as divs atm - it is more to advise that it is fine to use divs for layout you don’t have to use section for everything

    One other tiny thing. Well done on use of BEM. I’m glad you’re finding it helpful. Note you are not using it fully though. You can do modifiers like card 1 2 etc with a double hyphen. So use of a modifier class would be something like button button--secondary

    Marked as helpful

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