Design comparison
Solution retrospective
How much do you break your code into smaller files/components? Is it worth to bother with too many components on this level of complexity? Reviews of my solution and code are greatly appreciated. Thx
Community feedback
- @BismeetSinghPosted over 2 years ago
Hi, shouldnt there be a way to go directly from a country specific view to the home view directly, instead of clicking the back buttons dozens of times, once I am very deep into the hierarchy, I dont know whether its part of the challenge, but I just felt that from a user perspective and I couldnt find any. Alternatively, we could also do breadcrumbs that allow the user to jump anywhere in the so far navigated hierarchy, just my 2 cents.
Marked as helpful1@JT1974Posted over 2 years ago@BismeetSingh Thanks Bismeet for reviewing my solution! Yeah, I was thinking about adding a breadcrumb, or button to go directly back to the filtered, or unfiltered home, but as it was not in the project description, I finally decided not to bother with it. From a UX point of view sucks, I admit, and there's an easy fix for that, so I may do that later to have a better solution in my portfolio. Thanks for bringing this up! Cheers! 🙌
0 - @renrasPosted over 2 years ago
I usually break the page down into components when the code gets too long as it's easier for me to manage. Usually my jsx has like a maximum 100 lines of code. But only the ui elements and others that will be re-used will be stored in the
components
folder. The other page components I just store it in a page folder likepages/home
so that you wouldn't have to deal with a lot of unnecessary components in thecomponents
folderMarked as helpful1
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