Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Social proof section | grid, scss

Gutka•65
@karbowskam
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I think I did it right :) I did two break points: 375px and 1440px (previously I did one more in the middle).

However, I think I did something wrong with the background. Could someone check it out? :)

Thanks and hugs! :)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 4 years ago

    👋Hi Gutka! First, I can't find the CSS file on your GitHub repo 😅. I also had see the source code, but I couldn't open the CSS file.

    I have some feedback on this solution:

    • Heading order is important. You need to use h2 first, before you can use h3.
    • Rated 5 Stars... should not be a heading. Heading tags is used for titling section. If you think that is an important information, I recommend to use strong tag.
    • The alt value should not be hyphenated. It should be human readable and informative.
    • The star icons are decorative images. Remember, for any decorative images, you should leave the alt="" and add aria-hidden="true or role="presentation". Or you can just use background-image as Tediko said.
    • If you're going to use background-image, there's a gotcha. You need to change the width value on the icon-star.svg file to create a space. I recommend to increase it to 22 (based on Tediko Solution) to create a space on the right side of the icon, since you can't use margin or padding on background.
    • The feedback__name should not be a heading too.
    • For the alt value for the photo, I recommend to just fill it with their name. alt="Colton Smith".

    That's it! Hopefully this is helpful!

    Marked as helpful
  • tediko•6,700
    @tediko
    Posted almost 4 years ago

    Hello, Gutka! 👋

    Congrats on finishing another challenge! 🎉 Your solution looks good. Here's my few tips:

    • Less breakpoints doesn't necessary means better. Now, your solution isn't fully responsible. It does look good on mobile and on larger desktops but everything inbetween does look like mobile and it isn't good. Here is my old solution to this challenge just to illustrate you how it can behave across screen sizes.
    • You repeat your HTML code with star images which is unnecessary. Find the way to use only one star image. You can do it easily by using background-repeat approach in your css. To do this you'll have to create empty div and remove all img's.

    Good luck with that, have fun coding! 💪

    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

Oops! 😬

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

Log in with GitHub