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

Testimonials-Grid-Section (React and Tailwind)

react, tailwind-css
mehdias63•330
@mehdias63
A solution to the Testimonials grid 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,

    First off, great job on completing the Frontend Mentor challenge! It's a significant accomplishment, and your effort is clearly evident. I have a few suggestions that could help enhance your project even further:

    Screenshot in Readme File:

    The screenshot in your readme file is cropped. For future projects, aim to include screenshots that capture the entire view of your page. If your monitor is too small, you can zoom out in your browser to get a more comprehensive view. This helps in providing a better visual representation of your work.

    Main Element Width:

    It's a good practice to set a max-width on your main element. This prevents it from growing excessively wide on very large screens, which can lead to a less desirable user experience.

    Grid Implementation:

    You've done a nice job with CSS grid layout. For your next projects, consider using Tailwind CSS classes exclusively for setting grid properties instead of direct CSS. Tailwind offers a lot of utilities for grid layouts and can help maintain consistency and readability in your code.

    First Card Background Image:

    Your first card should include a background image. This would not only enhance the visual appeal but also align more closely with the design specifications.

    Component Naming and Styling:

    For the following component:

    export default function Grid({ icon, title, text, description, color }) {
      // component code
    }
    

    The name 'Grid' might be a bit misleading since the component represents a testimonial card. A more descriptive name like TestimonialCard would be more appropriate. Also, consider adding a box shadow (e.g., shadow-[40px_60px_50px_-47px_rgba(72,85,106,0.25)]) to match the design more closely.

    Defining Colors in Tailwind Config:

    Don't forget to define your custom colors in the Tailwind CSS configuration for your next projects. This will help in maintaining a consistent color scheme throughout your application and make your code cleaner and more manageable.

    Overall, you're doing an excellent job. Keep up the good work, and I'm looking forward to seeing your future projects!

    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