You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see that a huge amount of work has been done on the site. Getting the database up and running and the google maps api sort-of working, as well as building a carousel from scratch. It's a really impressive achievement.
I've got some questions though:
There appear to be some components that are nested along with the page.tsx file they're associated with (LogInForm.tsx), and others that appear to only be used on one page, but are in src/components. Are they intended to be used in multiple places?
We were encouraged by our mentor and product owner to avoid carousels in order to avoid accessibility issues that come from using them in the short time frame we have to develop. Have you considered some of those issues and what their solutions might be?
The search functionality looks super useful and detailed. But do you need to show all of the options at once? What about using accordions to reveal only categories the user is interested in? This might help to fit everything on mobile view.
Sorry have to go!
Wishing you the best of luck for your second sprint!!
The text was updated successfully, but these errors were encountered:
I can see that a huge amount of work has been done on the site. Getting the database up and running and the google maps api sort-of working, as well as building a carousel from scratch. It's a really impressive achievement.
I've got some questions though:
There appear to be some components that are nested along with the page.tsx file they're associated with (LogInForm.tsx), and others that appear to only be used on one page, but are in src/components. Are they intended to be used in multiple places?
We were encouraged by our mentor and product owner to avoid carousels in order to avoid accessibility issues that come from using them in the short time frame we have to develop. Have you considered some of those issues and what their solutions might be?
The search functionality looks super useful and detailed. But do you need to show all of the options at once? What about using accordions to reveal only categories the user is interested in? This might help to fit everything on mobile view.
Sorry have to go!
Wishing you the best of luck for your second sprint!!
The text was updated successfully, but these errors were encountered: