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

Responsive Testimonials Grid Section using CSS Grid and Sass Mixins.

sass/scss
P
Schindler Dumagat•380
@schindlerdumagat
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?

In this project, I was able to create a reusable CSS styles using Sass mixin feature. I was able to declare a set of CSS styles for the cards that I will be using for each testimonials. I just needed to declare it once and then reuse it everywhere which makes my code shorter.

I also used partial sass files to separate the base CSS styles and CSS resets styling, reusable CSS styles declared with Sass mixin and use it in my main CSS styles for the project.

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

The first challenge that I encountered is how I can use grid to create the layout for this project. So, I started reading some articles and researching more on this topic. After some careful reading, I was able to use CSS grid and implement the layout. Not the best implementation but good enoung.

The second challenge that I encountered is how I can write a reusable CSS styles that I can reuse for each testimonials. I decided to create a reusable CSS styles because I noticed that there are some common patterns each testimonials card has. So, I did some research I found the Sass will be able to help me with that with its mixin feature. I read more about this feature and afterwards, I was able to implement it in my project. Maybe far from perfect but it is good enough.

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

I wanted to gain some feedback on this project and how I can improve the code. Here is the list of my questions:

I declared my CSS grid layout template using this code:

main {
    height: 90%;
    width: 90%;
    display: grid;
    grid-template-columns: 1fr;
    justify-content: center;
    gap: 24px;

    @media screen and (min-width: 64rem) {
        height: unset;
        grid-template-columns: repeat(4, fit-content(15.938rem));
        grid-template-rows: repeat(2, 1fr);
        gap: 30px;
    }
}
  • Is there a better way of declaring the CSS Grid layout template for this project?

  • Did I use the correct HTML elements to markup my HTML? What HTML elements do you recommend instead for each project components?

  • Did I use Sass mixin feature to create reusable CSS styles correctly? I have a lot of parameters in my reusable CSS styles made with mixin, is that OK?

  • Sass Mixin and Sass Inheritance has a common goal in mind which is the reusability of CSS styles in the project. Is it better to use the inheritance feature instead of the mixin feature or my approach is good enough?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohamed Badr•80
    @Mohamed-Badr-Saad
    Posted 7 months ago

    It looks the same as the required design, however I think the background color should be "Light gray: hsl(0, 0%, 81%)"

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