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

React Practice Toggle (useState) and Fake Data Fetch (useEffect)

react, tailwind-css
tOnski86•330
@tOnski86
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?

Aside from the frontend design, I was able to practice frontend logic. I used React useEffect for a 'fake' data fetch for the FAQ items, and useState to manage the functionality of each FAQ item.

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

The logic to open and close the FAQ item while checking if it is open to toggle.

I was able to do it without multiple states, just checking the ID of the current open FAQ item with the id's of the items allowed me to open/close each item with respect to the others, basically opening only one FAQ item at a time.

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

Need to work on implementing animations for React state changes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan Heslop•2,440
    @dylan-dot-c
    Posted 9 months ago

    Well done! Design looks good!

    One issue with this is that the website isn't accessible, a keyboard/screen reader user can't toggle the dropdowns, I suggest you make the buttons actual buttons. You might also have to use some aria-* attributes to empower the a11y(accessibility) of your website. I'm not an expert and I myself need to do some research in that area.

    Also its good that you were able to use useEffect and create your own custom hook to fetch data, but you don't have to fetch the data from the json file, as you already have it and could easily export it as a data.js file and use the object there.

    I realized that on initial load there is a modal open, you could set the openModal state to an undefined value so all will be closed what you load the webpage. Anyways, well done, all the best.

    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