Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

HTML&CSS flex

Okaino•110
@Okain0
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


right now I do not know flex: grid, so I did it with flex: basis :)) I will be glad to any feedback, it will be interesting to listen to any point of view. /-------------------------------/ Thanks /--------------------------------/

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anthony•355
    @ACdev27
    Posted over 3 years ago

    I just saw one reason you excerpt text is too big on card. You are using h1 tag for these.

    First, only use one h1 tag per page. You might instead use h2 for these, or div, or p tag instead.

    But aside from that, h1 has its own default size (26px), but they should only be 20px.

    You need to at least set your own font size for h1 to override the default, and may want to also use a different tag such as h2, div or p for this text.

    Marked as helpful
  • Anthony•355
    @ACdev27
    Posted over 3 years ago

    It looks like each testimonial "card" is too large compared to design. I think you want to check the text size of Name and the first sentence/excerpt of text which seem too large.

    Also on very wide screens, the testimonials seem to stretch too wide. I had same issue. I corrected it by using a max-width: 1440 on my grid container.

    Marked as helpful
  • Hania B.•1,280
    @techanthere
    Posted over 3 years ago

    Hey Okain, seems some nice effort has been put in. One thing I have noticed while testing, the cards are not fully visible when the screen height decreases, the solution is that use min-height of 100vh, this will solve the problem. I can notice a lot of px units used, instead I will suggest using rem units wherever it is possible and using px rarely when it is required, this will make the content resize relatively. You should also check the accessibility report, always use the main tag for including all the content, this is a nice practice. Good luck :)

    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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub