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

Responsive Testimonials Grid Section | Advanced HTML & CSS

jpcardozx•100
@jpcardozx
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 the overall design and functionality of my project. The layout and styling came together well, and I was able to effectively implement responsive design principles to ensure the site looks good on various devices. I’m particularly happy with how I integrated the SVG elements to enhance the visual appeal of the cards.

Next time, I would focus more on optimizing the performance of the site, especially regarding image handling and code efficiency. While the design is solid, I noticed that image URLs sometimes lead to misalignment issues, and my approach to managing these assets could be more streamlined. I would also invest more time in testing across different devices and browsers to catch any inconsistencies early on.

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

Aligning and positioning SVG elements correctly within the card layout proved difficult. I struggled with ensuring the SVGs did not overlap with text or other elements. I resolved this by using absolute positioning with careful adjustments of the top, left, width, and height properties. I also used the z-index property to manage stacking order and ensure the SVGs remained in the background.

Handling images in production was challenging, as images often appeared misaligned or with incorrect dimensions when viewed live. I addressed this by adjusting the image CSS rules and using responsive design techniques, such as setting appropriate max-width and height properties. I also researched best practices for image optimization to reduce file sizes without sacrificing quality.

These challenges helped me learn more about CSS positioning and responsive design, and I will apply these lessons to future projects to enhance my problem-solving skills.

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

Image Handling: I often encounter issues with images becoming misaligned or not displaying correctly when the site goes live. I’d appreciate advice on best practices for managing image assets in production, especially how to maintain consistency across different devices and screen sizes.

Code Optimization: My current method of handling image URLs leads to heavy code and potential performance issues. I’m looking for suggestions on how to streamline my code for better efficiency and how to implement best practices for image loading and display.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Moh. Andrew Aprianto Putera•120
    @meandrewaprianto
    Posted 11 months ago

    hi jpcardozx. nice work already complete this challenge, for me. you should used a picture element and trying to used border. So you can get a perfect circle image with border around.

    Here's the link for picture element, picture element

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