Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 27 days ago

Testimonials grid section

bem
Tetiana•390
@TetianaAleks
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Andrey•3,890
    @dar-ju
    Posted 26 days ago

    Hi, Tetiana!

    Very nice work, done neatly, tags are almost correct.

    Look, this is a task on grid practice, you did not use all the grid features. You need to make a little more @media transitions, you only have 2 states - less than 1440px and more than 1440. On my laptop at 1360px the page looks like one narrow column. Your task is to check the work on all resolutions starting from 320 and ending with 1920. Grid allows you to conveniently manage elements. As the screen narrows, you can change the number of columns from 4 to 3 and so on.

    Next, about headings. It is not recommended to use more than one H1 heading on one page. This is not a full page, it is only a part of it, a component. It is assumed that the page will have an H1 header, use H2, H3 in the cards, but not H1.

    Before the release, use the HTML validator The code that does not have any warnings or errors will be considered clean.

    You get the idea about BEM, but usually the block is treated as a standalone component, like these testimonials. The review pieces themselves won't be reused.

    So you have whole component - class .testimonials, then the card is an element we get .testimonials__card, then the title is an element we get .testimonials__title or .testimonials__card-title - as you prefer, and so on.

    The third part of BEM is the Modifier, it is used when, for example, the cards have the same styles, but the background color of one of them is different, in this case it will look like this: <article class="testimonials__card testimonials__card--purple-background"> "purple-background" is Modificator, it describes the difference.

    Otherwise, everything is fine, it just needs some work. Good luck with your development!

    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 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