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

Faq Component using Flexbox, HTML, CSS, JavaScript

Dangelo•440
@Dangelobast
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?

Being able to learn why my content was shifting up instead of only going down when opening a question section, definitely use Grid next time and potentially make my life easier.

What challenges did you encounter, and how did you overcome them?
  1. background image, there are different ways to do it but my approach was using this property, it can get tricky when you go to smaller sizes but fixed it by moving my article or container up in specific screen sizes.

  2. Content shifting up due to how centering and some units work, to give more information when you set transform: translate 50% or top:50% to center content vertically it will affect how your content works meaning it will try to center suddenly when button is pressed creating this effect of shifting up, the way I solved it was using margin 0 auto and using top to a specific unit (in my case 13rem) then when it comes to queries just decrease this same unit so content still looks "centered" vertically.

  3. When viewport was too small when opening any question the content would be cut, this problems is due to my max height approach (to hide and show elements) since I just apply the class open-item with max-height:200px; then logically it will be 200px, guess what when viewport gets smaller paragraph will push down probably occupying more than 200px.

  4. Sometimes I hate javascript lol

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

Ways to approach background image and avoid content shifting up when opening questions as well as potential improvements for my JavasScript code.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Dangelo's solution.

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.