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

Responsive bootcamp testimonial slider HTML/CSS/JS !

accessibility, bem
Luqman (Luke)•320
@luqmanx1998
A solution to the Coding bootcamp testimonials slider 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'm most proud of actually completing this project haha 😂. This challenge ended up being much harder than I'd expected for a few reasons, particularly in the HTML/CSS, but it's probably just due to my inexperience. I honestly wanted to give up , but at the end of the day a dev can't give up so I managed to push myself to pull through. Again, I made some silly mistakes that ended up making this challenge MUCH harder than it should be, but nonetheless, I'm satisfied with the end result !

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

Surprisingly, the hardest part of this challenge wasn’t the JavaScript—it was getting the HTML/CSS layout just right! Working with overflow: hidden in the parent container of the slides added complexity to positioning and dimensions. I had to restructure my HTML and CSS multiple times to align with the design while keeping the slider functional. Initially, I struggled with positioning and image dimensions until I realized I’d forgotten to add a fixed height to the slider parent container. Without this, elements disappeared with overflow: hidden applied. Lesson learned! 😂 I’ll never miss that step again. I tried getting this pixel perfect, but I couldn't without a figma file as it would've taken too long, and also to be honest I would have to restructure my HTML/CSS to accommodate for pixel perfection.

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

Any feedback at all is much appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Katarzyna Kaźmierczak•260
    @KasiaKaz14
    Posted 9 months ago

    Hey, that's a really good work, and great you did not give up, and made it to finish the whole project. You can really be proud of you! HTML a CSS are connected with JS, so if you do not know them yet - I recommend you to start learning. Btw, if you really do not know them/have no experience I am impressed you were able to finish! Coming back to the project. The Javascript works correctly, but remember you can write functions inside the addEventListener. You do not have to separate it. If it comes to the whole design, there are a few things you can improve in CSS. Just take a look at the quotation mark, the text, slider or the "purple something" behind the img :D I must admit it's a good job, keep working :)

    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