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

responsive testimony grid section using html and css

anthony•170
@Codingtry123
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?

learn how to use scale to make the website more responsively

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

assign the space using grid template do the calculation carefully

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

when should I using relative unit for the length of container?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    MikDra1•7,450
    @MikDra1
    Posted 11 months ago

    Use relative units for container lengths when:

    • Responsive Design: To ensure the container adjusts to different screen sizes (e.g., vw, vh, %).
    • Scalable Layouts: When you want elements to scale proportionally with the viewport or parent container (em, rem).
    • Font Size Dependence: For containers that need to scale with text size, use em or rem.
    • Fluid Grids: To maintain consistent spacing and layout proportions as the screen size changes.

    Hope you found this comment helpful 💗

    Good job and keep going 😁😊😉

  • persanu13•120
    @persanu13
    Posted 11 months ago

    Strengths: The solution considers layout adjustments for smaller screens, which is beneficial for accessibility. Improvements: Alt text for images: Make sure every image tag, like <img>, has an appropriate alt attribute describing the content of the image. This is essential for screen readers. Color Contrast: Ensure that the color contrast between text and background is sufficient for users with visual impairments. You can use tools like the WebAIM Color Contrast Checker to verify this. Focus States: Ensure that all interactive elements (e.g., links, buttons) have visible focus states, helping keyboard users navigate your content.

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