Shortly: Responsive URL Shortening Web App

Solution retrospective
I'm proud that I was able to get the API call working, especially after troubleshooting persistent Cross-Origin errors. Initially, setting mode: 'no-cors' was resulting in 400 errors, and resolving that taught me a lot about handling CORS issues effectively.
Next time, I would consider using a component library like Material UI for a larger project to streamline styling and reduce time spent on custom UI work. I’d also use SCSS modules or styled-components to better manage styling scope and avoid conflicts.
What challenges did you encounter, and how did you overcome them?The biggest challenge I faced was resolving a Cross-Origin issue when making the API call. I spent a significant amount of time troubleshooting, including testing other APIs that returned successful responses. After researching online and exploring various solutions, I came across https://corsproxy.io/, which allowed me to successfully proxy the request and get the API call working. It was a great learning experience in debugging and understanding how CORS policies affect frontend development.
What specific areas of your project would you like help with?If the Figma file had included a tablet layout, I would have spent more time refining the responsive design for that screen size. I’d also like to improve the spacing and layout around the input box, especially by adjusting margins and boundaries more precisely using Flexbox for the container.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Amanda J Kendal-Brown's solution.
Join 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