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

FAQ accordion card using vanilla JS

placoderm•20
@placoderm
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The biggest challenge for me on this project was all of the images and the fact that some extended beyond a div and some did not. The background images were also tricky and I used some css that I hadn't before.

As well, the animations on the accordion were tricky, getting the rotate correct and closing the sections when new ones opened.

I really appreciated looking at the front end of other people's projects, both those that implemented everything correctly (because I didn't believe it was all possible!) and those that didn't so I could see the things I needed to focus on getting right.

I would appreciate feedback on:

  • the way I aligned the image
  • the way I structured the divs to allow the JavaScript to do its thing.
  • the opening and closing animation. I had to have a fixed height for the answers in order to animate this. I'd appreciate knowing another way to do it where I could use auto height and still get the animation.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Gurvinder Singh•580
    @Gurvinder-Codes
    Posted over 3 years ago

    @placoderm for the 3rd point you can simply set the display: none for the answer and then when the click event on the question is triggered, you can toggle a class with display: block to the answer.

    Hope this helps.

    Peace :)

  • P
    Pillippa Ignacia Pérez Pons•460
    @Pillin
    Posted almost 4 years ago

    Hi! I hope that you are well

    If you want to centered the layout vertically

    you can add in main tag

        height: 100vh;
        display: flex;
        align-items: center;
        justify-content: center;
    

    and in #card remove the margin. I hope It has been 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

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