Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

FAQs accordion with Astro

astro, react, tailwind-css, typescript, accessibility
P
David Inoa•150
@davidinoa
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Responsive Design and User Interaction

Achieving an optimal layout for various device screen sizes while maintaining interactive states for all elements was crucial to this project. I'm keen to learn about best practices in implementing responsive design with Tailwind CSS and any tips on improving the hover and focus states to make the UI more engaging and accessible.

Using Astro with React Components

Integrating React components within Astro presented unique challenges, particularly in client-side hydration and ensuring efficient rendering. I would appreciate feedback on optimizing React component usage in an Astro project. Are there any specific considerations or practices that could enhance performance or improve the overall structure when combining Astro with React?

Tailwind CSS for Styling

While Tailwind CSS's utility-first approach was instrumental in rapid UI development, I'm curious to know if there are ways I could further optimize my usage of Tailwind for better consistency and efficiency in styling. Any feedback on advanced Tailwind CSS techniques or practices I might have missed would be greatly appreciated.

I'm eager to hear your thoughts and suggestions on these aspects of the project. Thank you in advance for your valuable insights!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Tsukimi•820
    @hikawi
    Posted 9 months ago

    Perfect solution. I like the nice smooth animation also.

    I don't think you realized in the pretyped index.html file they provided in assets had the text content for the other questions tho lol

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