All solutions

What are you most proud of, and what would you do differently next time?

Disclaimer: There is some unfinished content still within this project. If you come across something that looks clearly unfinished, such as an empty page, then I likely already know about it. If you come across bugs or errors, however, please feel free to let me know in the comments as I am sure some things were missed.

I am proud of being able to implement as much as I was able to do. I spent more time on this project than I wanted to, but I learned a lot which is what it's all about. This was the first project where I did all the backend code myself (authentication, api data fetching, etc). Figuring out the authentication and implementing additional custom auth logic or custom fetch logic felt good.

Things I would do differently next time would definitely be to follow a more TDD approach. I went back and forth a lot with bugs because there were things that would work in local, but not work in prod. There were things that worked fine, but then upon adding new code to implement a new feature, those things that worked previously, would be broken now and I wouldn't notice until I looked around on prod. There was just a lot of things during the process that I think could've been avoided had I followed the TDD approach.

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

Sorting and filtering the fetch data proved difficult in certain parts. The part of this that I probably struggled with the most, was appending results to the pages when clicking the view more button. I had an issue where when clicking the view more button, it would replace the results on the page instead of appending to it. This took some trial and error to make work properly.

Implementing OAuth was a bit difficult as well due to never having done it before. I spent lots of time on stack overflow and talking to other people to figure out what I was doing wrong. Most of the time, the problems I had were just due to dashboard configurations in my google cloud profile and clerk authentication dashboard, not necessarily anything code related.

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

I feel like I wrote a lot of code with this project, I'm sure a lot more than necessary. I have plans to go back and heavily refactor my code as best as I can to adhere to better standards. There is a lot in here that is repeated, so centralizing certain pages/components/styling to cut down on project size is in the plans.

There isn't anything that I really need help with, but if you have any suggestions or ideas then feel free to leave a comment!

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

Initially, I attempted to use CSS Grid to align the tip selector elements properly. However, achieving the desired layout and responsiveness proved to be difficult with this approach. To overcome this, I switched to using Flexbox properties. I am much more comfortable with flexbox so I was able to achieve the desired layout.

I also faced challenges in customizing radio inputs to visually fit the design requirements. To address this, I opted to use div elements as tip selectors instead. By attaching JavaScript to these div elements, I was able to replicate the behavior of radio buttons. This approach allowed me to easily manage the active state of each tip selector, providing an experience that is no different in the users eyes.

What are you most proud of, and what would you do differently next time?

Between mobile, tablet, and desktop viewports, there was a lot of repositioning and resizing, so figuring all of that out to make this as responsive as possible felt good.

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

The fetch was something I haven't done very much of so working through that and adding the information to the page from the json based on what was clicked was a bit challenging but I just messed around with it and scoured stackoverflow until I was able to put together a working solution.

What are you most proud of, and what would you do differently next time?

Some of the css was tough when it came to the different viewports and getting everything aligned properly, but I was able to work it out. I still have edits to make to the tablet versions as there was no design for tablets and the images are at odd shapes and require a bit more work to look good on table sizes.

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

The form validation was something I'd never done so figuring out how to use a library like ValidatorJS was a learning experience and then getting everything styled correctly based on form validation was a learning experience as well.

What are you most proud of, and what would you do differently next time?

I was able to figure out how to calculate ideal weight range based on the inputted height. It wasn't a necessary part of the design instructions but it would have bothered my ocd if I didn't attempt to address it. So that was something that was a little confusing but felt good to figure out.

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

For the limitations section, I couldn't figure out how to position the boxes. I ended up using a combination of flex box and absolute positioning

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

I want to figure out how to not use absolute positioning here. I feel that there is a way to organize the limitation boxes in a way using css grid but I wasn't able to figure it out.