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

Next JS + Tailwind Testing

DerekL•225
@DplusK
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Has anyone tried tailwind in a project before, somehow when I am creating custom value on the 'tailwind.config.js' the default value doesn't work, for example I created 'circle' for height, using 'h-circle' then somehow 'h-full' or 'h-screen' doesn't work, similar thing happen with bg, I did have the purge on the config so I don't know if that's the thing that did it.

Also what actually is the benefit of using tailwind. Yes this project is not meant for using that but when dealing with repetitive styles its kinda annoying to keep making them, well I suppose I could have just used a loop for the data input, but still curious of what people think of tailwind.

Thanks for reading and sorry for rambling

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Miguel Dominguez•75
    @0wlofminerva
    Posted over 4 years ago

    the heading and the names of the white cards are over-enhanced, it might be a grey color instead. The quote symbol doesn´t match with the original, and counting on the accessibility html issues, but overall its achieved, under my humble poiint of view. congrats!

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Greetings, DerekL! 👋

    Nice work on this challenge! 🙌 Your solution looks pretty good and responds well! 👍

    The only thing I suggest is decreasing the space between the top of the page and the content of the page in the desktop layout. Currently, there's a lot of space between the two and I have to scroll down before I can actually see any of the testimonial cards. 😉

    Keep coding (and happy coding, too)! 😁

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub