Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Frontend mentor FAQ accordion challenge using basic js css and html.

Poum•40
@Poumdg
A solution to the FAQ accordion 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 am proud of my first working javascript code, since I only started learning it 1 month ago, being able to write this amount (although quite redundant and easy) without too much trouble felt nice!

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

I forgot how to target a specific css attribute (in this case visibility and display) in js and had to look it up on google.

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

I would like to know of a way to make my Javascript less redundant and more maintainable, but I am just a beginner so a beginner friendly advice would be best.

I also cannot resize the star image next to the FAQ heading below 40px in
@media (max-width: 400px); so I kept it at 40px. no matter how hard I tried. Is there a specific reason why? Any insight would be much appreciated. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jake Godsall•1,390
    @jakegodsall
    Posted over 1 year ago

    Hi 👋

    After taking a quick look at your code, it seems that the reason you can't resize the star image is because there are still max-height properties being applied to the image from the larger viewport media queries. This property is being overwritten with each media query decreasing in width, but in the @media (max-width: 400px) media query, you want to ignore this. A way to do this would be to set:

    @media (max-width: 400px) {
        .star_image {
            max-height: none;
            /* add width and height here */
        }
    }
    

    The sizing should work then.

    Taking a look at the JavaScript, there's a couple of things I would mention to reduce redundancy.

    The first thing would be to use classes that can be added and removed from the elements. For example:

    .hidden {
        visibility: hidden;
    }
    

    Then, you can use JavaScript to add or remove the class when the element is clicked:

    myElement.addEventListener("onclick",  function(event) {
        event.target.classList.toggle("hidden");
    });
    

    This will apply the CSS visibility: hidden property when clicked, and then remove it again when clicked again.

    Using this approach you don't need to have separate logic for applying styles and then removing them again.

    Hope this helps 😁

    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

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