Ticket Generator Vite-ReactJs-Tailwind- Router-dom

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

I'm proud of having created a fully accessible and responsive form with custom validations and dynamic ticket generation. I also managed the dual deployment (Vercel and GitHub Pages) with routing adapted to the environment, which was a great learning experience. Next time, I would plan the routing and deployment strategy further in advance to avoid last-minute adjustments. Additionally, I would explore automated testing to validate the form's behavior on different devices and screen readers.

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

One of the biggest challenges was configuring React Router to work seamlessly in both local development and static deployment on GitHub Pages. I solved this by using environment variables and conditional logic in both Vite and React, allowing the application to dynamically adapt its base name. I also encountered issues with image routing and Vite caching during deployment, which I resolved by cleaning up the build and carefully adjusting resource paths.

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

I'd love feedback on improving accessibility for screen readers, especially regarding dynamic content like post previews. I'm also interested in best practices for form validation libraries versus custom logic, and how to scale these types of forms for multi-step flows or larger applications.