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

REST Countries API

react, tailwind-css
Chris•400
@chrisvn188
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


Hi everyone, I'm so happy to share my solution for this challenge.

In this project I used ReactJs for building User Interface , TailwindCss for styling and Google Map Api for displaying Map for each country.

Although using TailwindCss to style is super fast but I find the code hard to read.

I used Google Map Api for the first time to add an additional map for each country. I think I can do some fun stuff with it. ( I deleted this feature due to the fact that it costs a lot of money)

I transform border countries to have more interesting look.

I want to make this project become one of my main portfolio projects. Can you guys suggest any functionalities to this project? I really appreciate that.

If you find any bugs or any suggestions, please let me know. Thank you for your valuable time and happy coding!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • NizarMjr•390
    @NizarMjr
    Posted over 2 years ago

    Good job #Chris I liked what you have done There is necessary thing you need to add to improve more you project : -Acces and get the details of country from the borders with this point you could make your project more wide and more accessible

    Good luck and Happy Coding

    Marked as helpful
  • Steven Portas•610
    @satrop
    Posted over 2 years ago

    Really impressed with the outcome you have here!

    I especially love the use of React! I am JUST getting into React and love the idea of compartmentalizing all the things.

    The only thing I would add is like the accessibility report says, I would get an H1 on the page, you could hide it with a utility class, but it's worth backing in as many ADA items as you can from the start.

    Really clean code. Noice work my friend!

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