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

Responsive page with grid(Desktop) & Flexbox(Mobile)

sass/scss
P
V.S Karthik Tirumalasetty•130
@VSKarthikT
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?

This project I am proud of using grid to make elements stay in the respective areas and stretch them to it full width and height in the container

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

I had difficulty with aligning items of the grid in desktop layout, I have read article about grid layout which made it easy for me to align items and gave me much deeper understanding of grid layouts

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

I would like help with reducing CSS code, how can I optimize the code, I am not sure I have use correct semantic HTML, any feedback is appreciated, Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 9 months ago

    Hi, @VSKarthikT

    I checked out your solution and I have some thoughts:

    HTML Suggestions:

    • For your .wrapper_[number] elements, consider using the article tag instead of div, as it gives more semantic meaning when wrapping content that feels article-like.
    • The .w_content[number] elements inside .wrapper_[number] might be redundant. You could apply the .w_content styles directly to their parent .wrapper_[number] and remove the extra elements for a cleaner structure.
    • For title[number], which seems to be each article’s heading, try using h1 instead of p tags. An h1 establishes a clear heading hierarchy, especially useful for accessibility and SEO.

    CSS Suggestions:

    • Many of your classes, like .title1, .title2, .title3, etc., have identical styles. You can simplify this by grouping them. For example:
    .title {
      font-weight: $CT_font-weight-title;
      font-size: $CT_font-sz-title;
      letter-spacing: 0;
    }
    
    • Try using min-height: 100dvh instead of height: 100dvh on body to prevent layout issues on mobile when the address bar shifts.
    • width: 100% isn’t necessary for section or block-level elements as they already span the full width by default. You can remove it to simplify the code.

    Hope this helps!

    Marked as helpful
  • Amit Dhakal•610
    @herojk64
    Posted 9 months ago

    Ok, if you want to reduce CSS the very first concept is to make as minimal html as possible. if you see your html there are few things I saw. why aren't you dividing your sections with section tag rather than div. you are just using section as main component which is nested in the main. I also don't see any header tag or h1,h2,etc. you see with the content you can separate the headers based on the title looking content. also article tags are best for that if you want to do better SEO. Anyway mixin in SCSS was a great find for me took me seconds to understand but didn't knew it was a thing in SCSS so thanks for that.

    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
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