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

FAQ Accordion Card with Flexbox and Grid

Fernando Mendoza•240
@whiteknight-dev
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I would like to improve my JS, if someone can help me I would appreciate it 😄.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vicktor•920
    @Victor-Nyagudi
    Posted over 2 years ago

    Hi, Fernando.

    Nice attempt on this one. I'm glad you used the BEM naming convention.

    I noticed you queried the DOM for all the questions and then added a click event listener on each one in your JavaScript.

    This works for a small solution like this one but is not the best for performance. In order to save on performance, you could attach an event listener to .card and get where the user clicks on using e.target.

    If the area the user clicked on is a question, you can then reveal the answer.

    Here's an example of what the code could look like:

    const card = document.querySelector('.card');
    
    // This is an alternative way of responding to click events. 
    
    // You can still use 
    // card.addEventListener('click', (e => { code in the function goes here e.g. console.log(e.target); }))
    
    card.onclick = function(e) {
       console.log(e.target); // <- Log to the console what was clicked on
    
       if (e.target.classList.contains('card__question')) {
    
          // e.target.chidren[1] gets the answer. Try logging it to the console to see what it returns
    
          e.target.children[1].classList.toggle('inactive');
       }
    }
    

    This isn't the whole solution, but you can build on it to improve your JavaScript.

    Hope this helps.

    All the best with future solutions.

    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