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

FE_Social-Proof-Section_Grady

Andrew Grady•175
@agr227
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


3rd challenge completed!

Thank you to the person who commented on my last submission!!! I was able to learn from how you positioned your CSS so it would be easier to follow.

Need help working on shortening and simplifying my CSS AND HTML if possible.

I really struggled with floating the elements in order to position them correctly. As well, I don't understand why certain elements appear where they do in the first place and not in the top left like I would assume after I float them. It's not an issue per se, I just have to insert extra CSS to reposition these elements.

As usual, forgive me if the preview appears differently. online than it does on the VS Code live preview.

Thanks!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mike Hayden-Moore•1,005
    @mickyginger
    Posted about 4 years ago

    Hi Andrew!

    Well done on this project!

    The reason why your images are not showing is because the img tag is not pointing to the correct location in your file structure. You do not have an image folder, but the img tag is trying to find an image folder.

    <img src="images/icon-star.svg" /> incorrect
    <img src="./icon-star.svg" /> correct
    

    You probably should put your images in an image or assets folder though, in which case the src would be ./images/icon-star.svg

    As far as the review elements are concerned, I think flex is your friend here.

    HTML:

    <div class="reviews">
      <div class="review">
        <div class="stars"> star images here </div>
        <p>Rated 5 Stars in Reviews</p>
      </div>
      <div class="review">...</div>
      <div class="review">...</div>
    </div>
    

    CSS:

    .review {
      border-radius: 10px;
      display: flex;
      margin-bottom: 10px;
      padding: 10px 20px;
    }
    
    .review .stars {
      display: flex;
      margin-right: 10px;
    }
    
    .review .stars img {
      margin: 5px;
    }
    
    .review:nth-child(2) {
      margin-left: 50px;
    }
    
    .review:nth-child(3) {
      margin-left: 100px;
    }
    

    It can sometimes be easier to think about the smallest element first and work backwards from there.

    Hope that helps!

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