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

Rest Countires API With Color Theme Switcher

react, vite, sass/scss
Gerry Lauriant•760
@GerryL2
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


Feedback Welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Krimothiazine•140
    @karim-saou
    Posted almost 2 years ago

    Hi there!

    I liked your design especially the animation.

    But there is some issues:

    1. responsiveness: I 'm currently learning responsive design so I am not the right person to give you nice advice but I would recommend you two solid resources that may help you tackle responsiveness: odin project source, a very straight forward and short course. Kevin Powell course. a little bit long but very high quality.
    2. In details page (chosenCountry as you name it), the border countries do not show! the solution is simple: get the border countries from the api => you get border countries in abbreviation => transform it to full name => finally use full name as a path inside <Link> component of react router library.
    3. in details page we do not need input search and filter by region , you can get rid of them by moving the code of input and filter to your <Country/> component.

    react router has adopt a new approach of routing and you are using the old approach, I would recommend you this free and splendid react router course from Scrimba, you will learn both the old and the new approach and which and when would you use one of them.

    Good luck!

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.

Oops! 😬

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

Log in with GitHub