Tailwindcss, Vue

Solution retrospective
I’m proud of how I handled the composables, especially the flow where more than one API request was needed. I created a utility composable to convert 3-letter border country codes into full country names, which kept the detail view cleaner and easier to maintain. I’m also proud that I stored the first API response in state so the main countries request only needed to run once, which improved performance and reduced unnecessary network calls. On top of that, I’m happy with the polish I added through pagination, theme switching, and final build/deploy validation, because it made the project feel complete and production-ready.
What challenges did you encounter, and how did you overcome them?Implementing light and dark themes with Tailwind was one of the trickier parts of this project. I got it working but feel there is room to improve the approach. That said I'm happy with how the end result looks. Making multiple API calls was an interesting challenge — the REST Countries API returns border countries as 3-letter country codes, so I had to make a second API call to convert those codes into readable country names. Working out the composable structure to handle that cleanly was a fun problem to solve.
What specific areas of your project would you like help with?I could have used some help/information on how to go about making API calls.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on stephenlit’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