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

Solution: REST countries API with color theme switcher.

accessibility
Leonardo Bomfim•90
@leubomfim
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


👋 Hello everyone 👋

This is the solution for the API countries REST challenge, it was very cool to solve this challenge, It was my first time doing a theme switch and I found it very fun, the API had a little difficulty in some parts.

I'll be happy to hear any feedback, or what could be improved in the code.

Thank you 👋❤️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmad_Mana•320
    @UserAhmad2001
    Posted almost 3 years ago

    Hello Leonardo,

    Congratulations on completing the countries API challenge 🥳

    Your solution is responsive and beautifully designed, I got a tip for you to make it even better.

    use the select and option elements in your region list for a more semantic code like this:

    <select>
    <option value='country value' > Country name </option>
    <option value='country value' > Country name </option>
    <option value='country value' > Country name </option>
    </select>
    

    Hope i was of help, Happy Coding

  • Adam-Hzi•100
    @Adam31-jpg
    Posted almost 3 years ago

    Hello I think you use the V3 api no ? If this is true can you tell me how to get the currencie and the native name of country pls ? Because in V2 it's easy but in V3 the api skeleton change

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 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

Oops! 😬

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

Log in with GitHub