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

Responsive Testimonial grid section using HTML, SCSS/CSS, and vite.

accessibility, bem, sass/scss, vite
Adesh Katiya•420
@adeysh
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 proud of creating it without struggling in the grid section. I would probably try to build these kinds of projects faster because it took me a lot of time to build it.

What challenges did you encounter, and how did you overcome them?
  • The challenging thing that I found was with setting up your project with base styles. I mean it probably took me a lot of time just for creating the base styles and also confusing about whether I am including any unnecessary base styles that are probably not required for this kind of project🤞😅.

  • The grid section was easy so I tried creating it with more detailed directory structure. Also used vite to setup the project and was confused where was it generating the css files 😂

  • Tried to use calc() and clamp() functions for the styles.

What specific areas of your project would you like help with?
  • I wanna learn how do you define the scale of the project. Here I have done probably a lot of complex organization because the same kind of styles can be created with less number of partials so if I am using a build tool is it necessary to be more organized and descriptive with the styles?

  • In all the starter files that you get in frontend mentor challenge, the style guide markdown file has a body copy font-size given. How do i figure out about rest of styles for heading? Is the method that I have used here correct or standard way or is there another way of doing this? If you can give me some tips or what you use, that would be really helpful for my future projects. So please provide me with your feedback.💫

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Salah Al-Din Kaki•140
    @Filostkana
    Posted 4 months ago

    will done adeysh

    • you do will with the semantic HTML
    • and I like how your code is structured

    ** keep do what are doing your great**

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