Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Social Proof Section Solution [Plain HTML + CSS, Flexbox and Grid]

accessibility
Faruq Abdul Hakim•580
@faruqAbdulHakim
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback or suggestions on this solution are welcome. 😉

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    First off, congratulations on completing your project, Faruq! Your HTML and CSS skills are clearly demonstrated in this Social Proof Section. Here are some suggestions to further improve your work:

    1. HTML Structure and Semantics:

      • Use more semantic HTML tags. For instance, replace <div> tags with <article>, <section>, or <aside> where appropriate for better readability and SEO.
      • Avoid using <div> for every element. Use <header>, <footer>, <nav>, etc., where applicable.
    2. CSS Improvements:

      • Consistent Naming Convention: Stick to a consistent naming convention for CSS classes to enhance readability. For example, choose between kebab-case (rating-container) and camelCase (commentContainer) and use it consistently.
    3. Responsive Design:

      • Implement responsive design using media queries to ensure your website looks good on all devices. You've done some of this, but ensure all elements scale well.
    4. Accessibility:

      • Alt Attributes: Good job using alt attributes in images. Make sure they are descriptive.
    5. Performance:

      • Optimize Images: Ensure images are optimized for the web to improve loading times.
    6. Code Organization:

      • Consider separating CSS into different files (modular CSS) for each component for better maintainability.
    7. Further Learning Resources:

      • HTML Semantics: MDN Web Docs
      • CSS Best Practices: CSS Tricks Guide
      • Responsive Web Design: A List Apart

    Keep up the fantastic work! Your dedication is evident, and every project you complete is a step towards mastery. Excited to see your future projects!

    Marked as helpful
  • Korney Chervonenko•1,080
    @KorneyChervonenko
    Posted over 1 year ago

    You remembered me about "flex-wrap: wrap". I should use it in next challenge. Thanks

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

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

Oops! 😬

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

Log in with GitHub