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

Responsive-Bootcamp-Testimonial-Slider-Made -With-GRID-FLEXBOX-and-JS

sass/scss, accessibility
Kamasah-Dickson•5,570
@Kamasah-Dickson
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 FrontendMentors. I made a solution for the bootcamp testimonial slider. I wanted to add an @keyframe class to the slider when the button is toggled but it seems the transition only happens once when I toggle the button. Well what do you think about my solution. I really need your opinions on this and please do not forget to like and comment. have a nice day :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Danilo Blas•6,300
    @Sdann26
    Posted over 3 years ago

    Hello Kamasah!

    I hope you can understand my comment as the button depending on how big the screen is can move out of the image.

    Personally I would create a parent div that has inside the image and the button, this div with positivon: relative (This div would occupy the same size as your image). And with that I would position the button with position: absolute and z-index: 1. And there I would begin to position it, since the button is currently positioned with respect to the <div class="right-img"> and depending on the screen the button would move lower or higher (I'm talking about the desktop view).

    If you manage to achieve that it will look good for all screen types.

    By the way the text and the user name have the following color if I am not mistaken hsl(240, 38%, 20%) and the sentences have a thinner font-weight for example font-weight: 200.

    And nothing you already know how to fix the errors in the report, the rest seems fine to me.

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