All solutions

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

Proud of my form validation and greater use of Components as Props (Children).

Next time, I would get back to a more disciplined approach to planning the development work before starting.

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

Challenge with using the "navigator" function to determine the Locale for currencies. This was caused because of the Server side Rendering which I ended up turning off for the relevant component.

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

I was happy with how I was able to create a really robust form with good validation. I would like to spend more time looking at how I can validate names (first name, last name) beyond just checking it is a string with a minimum length. Perhaps using REGEX or similar to reject non-alpha in the string might be a start.

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

This was fairly straight forward and the ByteGrad YouTube video at https://www.youtube.com/watch?v=u6PQ5xZAv7Q helped a lot.

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

How to validate names ina. more sophisticated way.

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

I am proud of how I was able to include a user login and a database backend to capture todos for each user. This took a bit of time but it seems to work OK now and includes two different login options (Google and Magic Link).

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

I had issues getting the magic link working in production when the re-direct url didn't load without a refresh. I ended up using a hack to get it working properly but never really understood the nature of the problem.

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

Understanding the Auth.JS "Resend" redirect in Next JS and why it worked in development but not production on the Vercel platform would be helpful.

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

I am proud of how I managed to get the two APIs working in react. Next time, I would think about the structure of my code a little more before executing.

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

I couldn't get the next JS 'error' page to move back to the home page after an error was created. For some reason the home page would not reload the page after using either the Link or Router.push("/) option.

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

Refreshing the home page after an error.

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

I am proud of how I am getting more and more discipline in the project structure and workflow.

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

I struggled with the positioning the background image.

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

He to keep the background image perspective the same as the screen size changes.

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

I was really happy with how the Cart content management worked out using Zustand for state management while the app is running and cookies with a 1 week life to capture state between app loads.

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

This was my first time incorporating GitHub Copilot into the workflow. It definitely helped speed up the development process but it is clear that you cannot blindly follow the suggestions without giving it some thought.

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

The biggest challenge was setting the Next JS Image component to enable the image to scale appropriately as the user changed the screen size. Thanks to Stack Overflow, I was able to resolve this fairly quickly.

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

None.

I struggled to create a Prisma schema for the backend database that could easily track the replies and associated dependencies. If anyone has thoughts here, I would appreciate them.

I find it a bit confusing working out which Type definition to use in Interfaces, for example the register and errors definitions (from react-hook-form) caused me a Biot of confusion. Does anyone have a good reference to look at?

I was not sure about the best place to put the actual fetch request - in the client component, in the Page.tsx file or as a seperate file. in the end I chose a seperate file to fetch the data. Is this the best approach?

This was tougher for me than it should have been. I particular, the floating cards caused me problems with trying to decide whether I needed to use absolute positioning or something else. In the end, it works but the code is not as neat as I would have preferred.

Difficulty overlapping and moving the two main sections into place.

Initially found it difficult to use react-hook-form. Also, ensuring the animation was triggered each time new dates were applied was a challenge for me.