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

HTML. SASS, and Javascript

Fazza Razaq Amiarso•2,320
@fazzaamiarso
A solution to the Coding bootcamp testimonials slider challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello!! Would love some feedback on my code. Especially on how the layout is done. Thank you in advance!!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. Layout is really great both mobile and desktop. Also the responsiveness is good.

    Some suggestions would be that:

    • on the body tag, you could remove the overflow: hidden declaration. I see that you use this to hide the extra spacing at the bottom right. To fix that, just add a align-items: flex-start on your main tag. The reason that happens is that, at default, display: flex gives the layout a default align-items: stretch

    This makes the layout or the item of the flexbox have the same size based on the largest or highest element inside of it. Since the highest (based on height) is the image, the text on the left side gets that size as well. And since you are using position: relative and top on the container on the left side, it pushes it down and creating extra space at the bottom. align-items: flex-start fixes that by only giving every element in the flexbox the height, based on the content of the element.

    • your slider togglers, the arrows, it is better to use button on it, wrapping the img of the arrowinside thebuttonso that it have extra accessibility, like when you usetab` on your keyboard to navigate.
    • The name of the person who said the testimonial could be wrap inside a heading tag like h2
    • Also, when creating website, it is convention to have atleast 1 h1 tag. On your solution, maybe adding a h1 tag inside the main tag, having the text like testimonials or any descriptive text that describes your website. But this h1 will only be for screen reader users, so this h1 will have a sr-only class, you can search only for sr-class. This is just css stylings that are intended for screen reader users.

    Overall, you did great on this, especially on responsiveness.

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