Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

testimonial-section using grid

cube-css
tushar-Ruhela•260
@tushar-Ruhela
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am most proud of thing like create grid section more good looking and this make me most proud and next time i am making better design.

What challenges did you encounter, and how did you overcome them?

The challenges are encounter like add box size of grid and urgest these boxes according to giving design,and i overcome them by knowing about particluar topic which i have need and apply them .

What specific areas of your project would you like help with?

yes , some area i want share like font and grid design and any one want give feedback on them .

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ortiz-antonio•270
    @ortiz-antonio
    Posted 8 months ago

    Hi,

    When I finished my project, the system asked me to give you feedback. I'm learning too, so feel free to correct me if I say something wrong:

    • Self-hosted fonts load faster because they don’t require an extra HTTP request, and you can take advantage of caching.
    • Pixel-perfect design isn’t necessary anymore. I used to make the same mistake! Here’s a great article on the topic: @JoshWComeau’s article.
    • The recommended minimum font size is 16px. Below that, text becomes hard to read.
    • You can use CSS variables to avoid errors and improve the readability of your code.
    • The desktop version is clipped below 820px
  • P
    newspaceracer•140
    @newspaceracer
    Posted 8 months ago

    Hi, Looks good. I like how you solved the progressively more specific rules, I think you used ID which is not usually preferable but you made it work! Couple of suggestions:

    • I would start the design with the mobile first and then do the media query for the widescreen version as that gives you most flexibility and helps making sure the smaller screens work better. Right now the size of the cards is fixed to be on the smallest card size even when the screen is still wide but not wide enough to go to the grid view. So something to keep in mind.
    • test your responsiveness on the browser and adjust the media query based on when it starts to break
    • You repeated a bit of declaration on the cards even for items that were the same card after card. I would try to give attributes to a parent container where the cards are so that it cascades to the cards within. That way you don't have to repeat yourself as much.

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