Interactive comments section using Next.JS and Tailwind CSS
Design comparison
Solution retrospective
What did you find difficult while building the project? By far, the most trouble I had was due to having my components inside the "pages" folder in NextJS. I spent a long time troubleshooting why the build kept crashing until I realized I just had to have a separate folder for my non-page components. Besides that, the replying system took me a while to figure out. But in the end it turned out fine.
Which areas of your code are you unsure of? Passing down props feels a bit overkill at times. Maybe there's a way to limit the amount of props I have to write down. I also haven't managed to give the plus/minus button a change of colour on hover. If someone knows a good way to do this, feel free to let me know.
Do you have any questions about best practices? Regarding the props, I'd say. Passing down a bunch of props through layers of components feels a bit prone to bugs. If there's a better way to manage props, do let me know!
Community feedback
- @0xabdulkhaliqPosted over 1 year ago
Hello there 👋. Congratulations on successfully completing the challenge! 🎉
- I have other recommendations regarding your code that I believe will be of great interest to you.
HEADINGS ⚠️:
- This solution has generated accessibility error report due to lack of level-one heading
<h1>
- Every site must want at least one
h1
element identifying and describing the main content of the page.
- An
h1
heading provides an important navigation point for users of assistive technologies, allowing them to easily find the main content of the page.
- So we want to add a level-one heading to improve accessibility by reading aloud the heading by screen readers, you can achieve this by adding a
sr-only
class to hide it from visual users (it will be useful for visually impaired users)
.
I hope you find this helpful 😄 Above all, the solution you submitted is great !
Happy coding!
1 - @davidpagebytePosted over 1 year ago
Hi, checkout Redux, this tool is designed to avoid props drilling
0
Please log in to post a comment
Log in with GitHubJoin 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