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

Social-Proof-Section (React and Tailwind)

react, tailwind-css
mehdias63•330
@mehdias63
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ehsan Tatasadi•1,800
    @tatasadi
    Posted over 1 year ago

    Hey there,

    Firstly, fantastic job on the challenge! It's evident that a lot of effort and skill went into this project. I do have a few suggestions that might help in refining the code further:

    Regarding the Social Component:

    The current implementation uses a component just to render an image:

    export default function Social() {
      return <img src="/images/icon-star.svg" alt="icon-star" />;
    }
    

    While modularizing is generally a good practice, in this case, it might be an over-abstraction. Unless there are additional functionalities or complexities anticipated for the Social component in the future, directly embedding the image where it's needed might be more straightforward.

    Naming and Structure of the Count Component:

    The Count component seems to be more aligned with the functionality of a testimonial card. A more descriptive name like TestimonialCard would better reflect its purpose:

    export default function TestimonialCard({ icon, title, text }) {
      // component code
    }
    

    Also, assigning a fixed height to the card (h-[15.5rem]) could lead to content overflow for longer texts. It's generally better to let the card's height adjust based on its content.

    Styling of the Main Element:

    Avoid setting a fixed width and height for the main element. Allowing it to grow and adapt to different screen sizes and content lengths is usually more effective for responsive design.

    CSS for Card Alignment:

    The current approach to aligning cards using margins in the media query is not ideal:

    @media (min-width: 64em) {
      div.btn:nth-child(1) {
        margin-left: 1px;
      }
      div.btn:nth-child(2) {
        margin-left: 35px;
      }
      div.btn:nth-child(3) {
        margin-left: 65px;
      }
      div.wrap:nth-child(2) {
        margin-top: 50px;
      }
      div.wrap:nth-child(3) {
        margin-top: 80px;
      }
    }
    

    Instead of manually adjusting margins for each card, consider using CSS Grid. Grid layout offers a more dynamic and flexible way to arrange elements, especially for responsive designs. It can automatically handle the spacing and alignment of cards, reducing the need for specific margin adjustments.

    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