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

React REST Countries API

react, react-router
Kamelek1337•190
@Kamelek1337
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 most proud of how well the country search works but I would definitely use a different API as this one gave me a lot of trouble displaying the data correctly

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

As I wrote above, I had a problem with properly displaying data from the API and with hosting the entire website because I was using React Router. Eventually, I managed to find an article that explained to me that you need to use other commands than usual in the console to publish a page on GitHub

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 11 months ago

    Hi @Kamelek1337,

    Nice project! Here are a few suggestions for improvement:

    Mobile-First Approach: Your site currently isn’t responsive. To make your site easily responsive, consider using a mobile-first approach. Think of your site as a tower: if you start by building a solid foundation (mobile design), it will be easier to expand and adapt for larger screens. If you start with the top (desktop design), you’ll need more CSS to fix issues on mobile devices.

    Mobile is the most important device nowadays, so ensuring it looks great on phones first is crucial. Use media queries to adjust the design for larger screens after establishing a solid mobile base.

    Translate Border Names: To improve user experience, consider translating border abbreviations (like FRA) to their full names (e.g., France). This will make your content more accessible and understandable for all users.

    Hope this was helpful

    Best, Teodor

    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