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

FAQ Accordion built with React and TailwindCSS

react, tailwind-css, typescript, accessibility
Jenny Eikens•250
@Jenny-Eikens
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 most proud of having learned a new CSS framework. Having tried Bootstrap out in the past, I found that it was too rigid and didn't allow for enough customization. With Tailwind, I like that it is utility-based and lets me customize everything while minimizing the amount of typing I have to do.

I also like that this time, as opposed to past projects, I focused on building the structure first before worrying about styling.

With my next project, I would like to learn more about grid layouts and implement those, as I currently mostly use flexbox. I'd like to understand more about the intricacies of grid and when it might be the better option.

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

I encountered two main challenges.

The first is that I couldn't get the background svg at the top to be the right size / to take up the right amount of space on the page. I tried setting its width to 100% and adjusting its height, but I found that it would never span the full width of the viewport unless I set the background size to contain. However, doing so prevented me from adjusting the height. I have not found a solution for this.

The second "challenge" (though it was more of a learning experience than a challenge) was that I worked with Typescript for the first time, which had me running into some issues where variables' types weren't defined properly or were contradictory. However, this was actually helpful as it helped me catch logic errors that I otherwise would've missed.

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

As described above, I failed to get the svg for the background image to be the right size. The image currently takes up too much of the viewport height, but if I don't use background-size: contain, the image won't take up the full width of the viewport despite setting it to 100%. I'd be grateful for insights from others and advice on how to solve this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chris•90
    @Chris-Wagg
    Posted 9 months ago

    Hey. A solution for your background issue could be to use pure CSS instead. The image itself it sized to be 1440px wide so if you set a background on the body and have no-repeat then it should fit itself within the space. 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

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