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

Testimonials grid section [HTML + Tailwind CSS]

tailwind-css
Arunkumar S•100
@arunkumar0398
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have completed the challenge Testimonials Grid Section 🥳

Languages that I have used 🧰

  • HTML
  • Tailwind CSS

I would welcome any feedback or suggestions for improving the solution on this challenge. Feel free to leave your comments below. 🙏

** Happy Frontend Mentoring ** 👍

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bishal Singh Deo🎮•1,440
    @Bishalsnghd07
    Posted over 1 year ago

    Hi, @arunkumar0398👋

    Congrats for completing this challenge🎉 and great work👏

    This challenge is specially made for enhance your skills in grid not in flex. I did not see any grid or any grid properties in your code, somewhere flex should be used, like in child div's not in all. I'm telling you this challenge is very good for upskilling in grid properties. I will recommend you to, if you don't know grid property, then learn some basics from youtube or anywhere and then take pen and paper and make the grids in which div you want. It will help you to come closer to the desire result with better approach for this challenge. And if you using grid in it, then you did not have to write this large number of code you have been written, it will be done it very easily way. By doing this code scalability will improve and also you will be become one step closer to responsive layout.

    Hope, this small tip will help you.

    Happy Coding❤️

  • Olaniyi Ezekiel•7,580
    @Ezekiel225
    Posted over 1 year ago

    Hello there 👋 @arunkumar0398.

    Good job on completing the challenge !

    Your project looks really good!

    I have suggestions about your code that might interest you.

    📌 First: Use <main> to wrap the main content instead of <div>.

    Tags like <div> and <span> are typical examples of non-semantic HTML elements. They serve only as content holders but give no indication as to what type of content they contain or what role that content plays on the page.

    📌If you don't have the Figma design files, I recommend using a browser extension called Perfect Pixel.

    It allows you to compare your finished project with the design images that come along when you download the project and check the (almost exact) dimensions. It's very useful!

    📌Learn more about Media Queries: Media queries are an essential part of responsive web design. They allow you to apply different CSS styles based on the characteristics of the device, such as screen width, height, orientation, and resolution. You can start by reading articles or tutorials on media queries to understand how they work and how to use them effectively.

    Practice: The best way to become familiar with media queries is to practice using them in your projects. Start with simple layouts and gradually increase complexity as you gain confidence. Experiment with different breakpoints and CSS rules to see how they affect the layout on various devices.

    Use a Mobile-First Approach: One popular strategy for responsive design is the mobile-first approach. This means designing the layout for mobile devices first and then adding styles for larger screens using media queries. This approach helps ensure that your website looks good on small screens and then adapts to larger screens.

    📌Understanding the importance of using External CSS over Internal CSS is crucial for writing cleaner, more maintainable code. Here's why you should make the switch:

    📌Separation of Concerns: External CSS allows you to separate the structure (HTML) from the presentation (CSS). By keeping your styles in separate files, your code becomes more organized and easier to manage. This separation makes it simpler to update or modify styles without affecting the HTML structure.

    📌Reusability: With External CSS, you can create a single stylesheet that can be linked to multiple HTML files. This promotes code reusability, saving you time and effort by avoiding duplicate styling code across your website.

    📌Ease of Maintenance: Imagine having to update the styling of your website across multiple pages. With External CSS, you only need to make changes in one central stylesheet, rather than hunting down and updating each individual `` tags in your HTML files into this external stylesheet. Then, link your HTML files to the external stylesheet using the <link> tag in the <head> section:

    <link rel="stylesheet" type="text/css" href="styles.css">
    

    By adopting External CSS early in your coding journey, you'll set yourself up for success by writing cleaner, more maintainable code that is easier to collaborate on and update as your projects grow.

    I hope this suggestion is useful for future projects.

    Other than that, great job!

    Keep up the excellent work and continue to challenge yourself with new projects. Your progress is impressive, and each project is a step forward in your front-end development journey! 🚀🌟.

    Happy coding.

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

Oops! 😬

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

Log in with GitHub