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

REST Countries API with color theme switcher (React)

react, sass/scss
P
Antoine•330
@super7ramp
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 think implementation works as expected and is close to the design.

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

It was fun to implement, I learned a lot of things!


🤔 There are a lot of flag images to load for the front page. How to lazy load them?

✅ Just add the loading="lazy" attribute!


🤔 How to implement a color theme switcher?

✅ Like this:

  1. Determine which theme to use initially
  2. Set it as a data attribute (e.g. data-theme)
  3. Implement a few CSS rules to change foreground and background colors based on this attribute value
  4. Toggle attribute value upon click on theme switcher button
  5. And voilà!

🤔 How to customize the region picker without JavaScript?

✅ Learn about customizable select elements!

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

Any advice/feedback welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jan Kotvaš•460
    @DrakeHermit
    Posted about 1 month ago

    Good job on finishing the project. One thing I noticed immediately after I went to look through your code is the fact that you committed the figma file which is not something you should do. Also you committed the .env file too which should never be committed since it holds your secrets, even if it's not that bad since you only had the url to the API there it's still not the best idea to commit your actual .env file After looking through your actual src folder I noticed that you include a lot of logic in your components while that's not bad by any means it's usually better if you extract the logic into separate functions and then import them into your main component. Also you honestly really don't need to comment your code that much. I also noticed some inconsistencies with the actual design file but that's not that big of a deal honestly.

    Overall you did a great job Happy coding!

    Marked as helpful

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

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub