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

Testimonials Component

sass/scss
TheRoboRobin•160
@TheRoboRobin
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 extremely proud of the way I implemented the concept of "pseudo private properties" as presented. I think it went a long way to keeping the variants organized and minimize repeated code. I'm still having trouble with the responsiveness of grids and using minmax, auto-fit, etc. to achieve it. So maybe I would have approached the grid differently.

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

My biggest challenge was thinking responsively when building the grid sizing. I think what I ended up doing worked but I still have some learning to do for sure.

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

I want feedback on the cleanliness of my code, the architecture, and the responsiveness of the page. What can I do better?

I'd also like to hear what you think about the "pseudo private properties" that I implemented. Is this concept good to use? Is it misguided? Will it cause problems later down the line that I'm not thinking of?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Akiz-Ivanov•450
    @Akiz-Ivanov
    Posted 4 months ago

    It's perfectly fine solution. Responsive for all the devices.

    For the future I've seen people mention on the web that using font-size: 62.5% on <html> might not be great because it can impact user experience for those who like to change default font-size in their browser settings (mostly older people or those who have bad eyesight).

    There's a pretty good video on youtube with some other practices on how to convert px to rems. I personally like using the sass function.

    However, if font-size: 62.5% works best for you stick with it.

    You used sass "pseudo private properties" good. I don't know if there are any downsides to using them, i haven't encountered any problems yet.

    It's a bit of a tricky grid layout; you did great to make it responsive. You probably would've had a bit less work to do if you used grid-template-areas instead of grid-column and grid-row. But the result is the same.

    Also, there was an SVG in starter files for the decorative quotation marks in the background, but using ::before works perfectly fine too.

    Final product is top-notch 👏, have fun with future challenges.

    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

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