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

coding-bootcamp-testimonials-slider HTML, CSS & Javascript

AbdulKareem•170
@seniorteck
A solution to the Coding bootcamp testimonials slider challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


hi everyone, this is the second time I am taking this challenge, the first time I did it then 3months ago I could not figure it the layout, I almost give up but seeing how people are trying their best every day to solve the challenge so I left for a while to learn HTML & CSS again from scratch, so yesterday I decided to pick it up again to my surprise I did what I could not do then, although am not sure about every step I used if it the best practice but I am open to feedback. And a great thanks to those that comment last on my last project, they recommend great resources which I will go through all after I submit these. thanks a lot to this great community, whoever that have found it has helped 90% on my journey of learning to code...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • AbdulKareem•170
    @seniorteck
    Posted over 4 years ago

    thanks a lot, I will definitely check out the BEM been told that but I don't seem to know the meaning but I just copied "BEM" and I paste it to google, I was amazed to see what I am missing about it, will be back with implementing it on my next project

  • Salko Balić•40
    @thedev966
    Posted over 4 years ago

    It's always easy to give up but whenever you feel like losing your motivation to keep it up, always do recall the reason why you even started this programming journey! Life is not meant to be easy, it's full of challenges you have to pass or just give up like a coward xd.

    Something you can improve:

    1. Your footer has an ugly transition on hover event. Use transition css property to fix it.
    2. css and js folders should not be inside of assets folder. Place them in the root directory
    3. You have uploaded styleguide file, design folder and screenshots folder for no reason to your github repo. Remove them.
    4. (Optional) Look up "BEM - Naming convention" and try to use it in your next project. It's the best way (imo) to name your css classes and keep it as clean as possible.

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

Oops! 😬

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

Log in with GitHub