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

Product feedback app using Next.js

accessibility, mongodb, next, tailwind-css, typescript
Mateusz Bizoń•330
@mateuszbizon
A solution to the Product feedback app 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 really like the select dropdown component I have made which is in home page and in create/edit page. Especially I love that make the accessbility for this which is field I always skip. One thing I would next time to add some aria-label for the elements and switch ul list items with up/down arrows not just with tab press.

Superb thing that made is that the whole project works as full-stack application with back-end not only front-end. It is not first time I have created full-stack app but anyway I really like the whole project and how it works. Next time I would try to create own backend in Express.js and try to implement custom authentication.

Next thing I always forget is to add semantic html tags. I always remind myself of this in half project or in the end.

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

My main challenge that I tried to do completely alone was to make ul list which behaves as dropdown to be accessible. At the begging it was very hard for me and every idea went unsuccess. Solution for this was only to add tabIndex attribute.

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

In the project every page component is client component because I am using tanstack query for getting data from backend. I wonder if the page component in Next.js should be always as server component or it can be as it is now in this project?

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 Mateusz Bizoń'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 1st-party linked stylesheets, and styles within <style> tags.

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.