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

Responsive FAQ accordion card using Flexbox

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

Solution retrospective


I think my design looks similar, but I had a lot of difficulties with CSS part (to locate image, cube, and especially shadow on desktop layout). I feel like I did it in a strange way. Is it supposed to use negative margin/absolute positioning or transform-translate for creating such 3D layouts...? Any feedback is very welcome!!!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shahin NJ•1,190
    @SJ-Nosrat
    Posted almost 4 years ago

    Hi Anna, Wonderful solution! I've looked at your CSS and noticed the following;

    1. On the .faq-text class; you can change the overflow-y: auto; to overflow-y: hidden; that'll get rid of the scroll when you open the accordian.
    2. With regards to positioning the box; you can remove the transform property and add: top: 8.85rem; and left: -7rem; that should place the box nicely giving the shadow effect. Or as you've used transform with the following values: transform: translateX(-62%) translateY(35%); either approach is perfectly fine; that's the beauty of coding.

    With regards to negative values, MDN documentation mentions the following for top: A negative, null, or positive <length> so it's perfectly fine to use negative values.

    Once again well done! Looking forward to your other solutions!

    Keep on coding and best of luck with your coding journey!

    Marked as helpful
  • bunee•2,020
    @buneeIsSlo
    Posted almost 4 years ago

    Hey @Anna60991, Your page looks great and is completely responsive, Great job!

    However, I did notice a bug. you can experience this by clicking right under any of the questions. doing this reveals the answers of every question and gets quite tricky to toggle them back off. I think the reason behind this is the event listener on the li tag, If this is the case... I think adding the event listener to the div with the class of question should solve this issue.

    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
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