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

Testimonial-Grid-Section using HTML5 and CSS3

Shreya Bera•55
@shreya-bera
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


It will be my pleasure to have feedback for my code!!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Szymon Rojek•4,540
    @SzymonRojek
    Posted over 4 years ago

    Hi Shreya,

    Well done :D

    I have checked your HTML structure, CSS, a few tips for me:

    • every testimonial you can treat as a article with header;
    • I think status (graduate) doesn't have to be the heading;
    • this component we can see as a single page component so also we can add the h1 tag, for example for screen readers => sr-only class with hidden;
    • possibly the blockquote can be also added;
    • I would suggest to use readable classes (descriptive) => If you didn't learn BEM I'd recommend to start learn it;
    • remove styles from CSS and transfer them to the CSS file;
    • in this project it will be better do not leave an empty alt;
    • reset the styles by adding selector * { margin/padding 0 and box-seizing: border-box };
    • don't add height and width to the card (that's a reason why you have to learn flexbox or grid => sometimes we have to add height or width but depends on the project);
    • in this project don't use position relative or absolute;
    • it will be better to start building project from mobile first with one column, then for tablets: create two rows with two boxes each and below the 5th box for the entire length of the container and finally: desktop design pattern;
    • check your HTML issue report (try to six it).

    In the end, @sayide mentioned already about it, but I'd recommend firstly start to learn flexbox and when you will be confident with it start to learn grid (don't rush, it will take some time and it is better to learn slowly but effectively) => then you will be able to create good RWD for mobiles, tablets, desktops. Also, about headings: when you want to start your HTML5 structural elements with a h2 (if h1 has been used on the page of course) and then you have to move down the levels gradually if there are other subheadings.

    Two courses providing by Wes Bos for free:

    • flexBox;
    • grid.

    Greetings :D

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey, Shreya Bera! 👋

    Nice effort on this challenge! 👏 The desktop layout of your solution looks pretty good! 👍

    Like SeyideHundeyin helpfully suggested, looking into and using CSS grid to create layouts like this will make things much easier for you when creating the layout itself and making it responsive! 😉

    I also suggest taking a look at your solution report and trying to clear up some of the errors that are there (it seems that you used some backslashes instead of forward slashes in your file paths).

    Keep coding (and happy coding, too)! 😁

  • seyide hundeyin•440
    @SeyideHundeyin
    Posted over 4 years ago

    Hi Shreya,

    I would recommend using CSS grid for this challenge and also stick with using h1-h6 without jumping from h1 to h3.

    Also on mobile, it doesn't sit in the middle you can use "margin: 0 auto;" to centralize your container.

    You can learn more about CSS grid here: https://www.youtube.com/watch?v=jV8B24rSN5o&ab_channel=TraversyMedia

    Hope this helps!!

    Keep coding and happy coding!!

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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