Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Social proof section

Kaung Lun•110
@lunk-kml
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Mobile version and desktop version are completely different and that was my challenge.

My other challenge is getting the ratings box and the buyers box to appear next to each other BUT not in a straight line next to each other. I did my best to do that.

When building this project, I find difficulty in making the entire body to be center for the desktop version. I think I made a mistake with the margin or something else. Not sure.

Overall, I'm glad to push through BUT I think my CSS code is very messy.

Feel free to take a look at my code and my final result. Point out any mistakes I've made. Give me any lessons, tips, feedbacks, or ideas. I still have more to learn.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 2 years ago

    Hi! 👋

    I suggest removing the alternative from all the star icons (alt=""). Those are decorative images. They don't add any meaningful content for the users. Also, they create a lot of noise for screen reader users.

    Here are some more suggestions:

    • There should not be any inline styling. Put all the styling in the external CSS.
    • Wrap the quote with blockquote.
    • Remove the word "picture" from the alternative text. There's no need to tell the users that it is a picture or image since you are already the img tag.
    • Use the em unit for media queries. It adapts when the users change their font size setting. Here are some references.
      • @media - CSS: Cascading Style Sheets | MDN #accessibility_concerns
      • PX, EM or REM Media Queries?
    • Prefer unitless numbers for line-height values to avoid unexpected results. The MDN documentation of line-height explains it well.
    • Use single class selectors for styling whenever possible instead of id. id has high specificity which can lead to a lot of issues on the larger project. It's best to keep the CSS specificity as low and flat as possible.
    • There's no need for absolute positioning. You can use flexbox to align the ratings with the text on the desktop layout.
    • To make the content in the middle of the page, I suggest making the body element as a flex container. Then, set min-height: 100vh to make the content vertically center.

    I hope this helps! Happy 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 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