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

My Faq Accordion Card Solution with React

Elena Barden•170
@metehnay
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


after spending hours i gave up illustrations positioning. still look ok i guess.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Millz•530
    @Brezus
    Posted over 3 years ago

    very good the accordion works great and the layout is good here are a few suggestions :

    1. Your .container class has a height of 100vh i would change that property to min-height: 100vh In your .container-md i noticed you are setting max and min heights generally it is considered bad practice setting heights because it can cause problems we were not expecting so instead let the content eg paragraphs, images or any htmls content to dictate the height of said container.
    2. On .container-md you also set min/max width those can be confusing and they are set to the same value in your code.. what i like to do is set a regular width eg. 'width:80% or width: 80vw' and under it put a max-width of 1000px so it never gets wider than 1000px.
    3. I would remove all the images in your .faq div and set them to be background images check out how to set background-images, how to position background images and how to chain more than one background image. Here are links that could help you out https://developer.mozilla.org/en-US/docs/Web/CSS/background-image, https://www.w3schools.com/css/css3_backgrounds.asp hope this helps

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