Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 months ago

REST Countries API with color theme switcher

react, tailwind-css, typescript, vite
Sophie•430
@ippotheboxer
A solution to the REST Countries API with color theme switcher challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I'm proud of myself that I could make this work. I struggled a lot with this project since my knowledge of React wasn't that great besides using useState and more simple functions, and also it was my first time using tailwind so I had to go back and improve the responsive styling.

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

I really struggled with this initially and actually gave up and thought I couldn't do it. After I learned more about context in React, I could do it, by applying the search input and filter region as context that change the response when mapping. I couldn't figure out how to make this work, but now that I know more about React, I realized it wasn't too complicated. Also when hosting with GitHub pages it didn't work, so I used render and this was better since I didn't have to change any existing code. There was also a lot of errors with missing data for certain countries so I had to handle the data when received.

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

I don't think the styling was done in the best way so I would appreciate some advice with that. For example the country image was always a different size even though I used w-[...px] h-[...px] to control the exact amount of pixels, it always seemed to be a slightly different size.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Sophie'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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.