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

Back on track after a while, Responsive

Nam Haϕ820
@Nam-Hai
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Quick coding, so not the most effective way to implement everything. I had not code for a while so don't mind reminding me things i forgot, especialy on the html/css structure.

I struggled with the background so it don't creat a scroll bar, so i did what i beleive to be a dirty trick with overflow-x: hidden

I tried to implement the 5 stars with background repeat but i couldn't find out to space out the stars without going on photoshop and resize the original icon. So i just implemented 5 <img> x3 times, which i think is not ideal for cache purpose. Tell me if there is a better way.

Thx a lot

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 3 years ago

    Hey, awesome work on this one. Layout in desktop looks great, it is responsive, however you you are using too much screen-size for the mobile layout. Right now, at point 1200px going down, the mobile layout is already being shown, desktop layout could have used more of those screen-size. The mobile layout however looks great as well.

    Some other suggestions would be:

    • Avoid using height: 100vh on a large container especially the body tag, this makes the element's height limited to only remaining screen/viewport's height, try inspecting your layout in dev tools at the bottom, hover on the body tag, you will notice that it doesn't capture the whole content. Instead, use min-height: 100vh this takes full height and will expand if it needs to.
    • For this one, I wouldn't use header I would just use main to wrap the whole content since the contents is just one component or a section.
    • The text after the h1 should be using p tag, use meaningful elements on any content, you could wrap the span inside the p tag or just use p tag on it.
    • Each img of the stars should be using alt="" attribute as well as aria-hidden="true" on it, since it is only decorative image, hide it. Also, always remember to include the alt attribute, don't forget to include it.
    • Again the text for the ratings should be wrapped inside meaningful element like p tag.
    • Each person's image should be using their name as the alt value like alt="Colton Smith", if an person's name and image is present at a page, always use their name as the alt value.
    • Great that you use heading tag on the person's name, but the heading level is wrong. If you use h3 make sure that h1, h2 are present as well, use heading tag with their level incrementally by 1.

    Aside from those, site looks great.

    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