Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Custom-designed Countries REST API

react, tanstack-query, react-router, typescript, styled-components
Lee•170
@tripkmin
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


※ For this challenge, I only met the minimum specifications of the design guide and made changes to suit what I wanted to implement.*

🔗 Links

  • Github URL: Click here
  • Live Site URL: Click here

🛠️ Technologies Used

  • React JS
  • React Query
  • TypeScript
  • Styled-Components
  • Framer Motion
  • HTML5, CSS

🗒️ Core Features

  • Browse all countries on the home screen
  • Search for countries using an input field
  • Filter countries by region
  • Click on a country to view detailed information on the Nation Detail Page
  • View and navigate to neighboring countries on the Nation Detail Page
  • Responsive design implementation
  • Visual feedback for all interactive elements on the page
  • Implemented Light Mode and Dark Mode

⚡ Additional Features

  • Custom Design
    • Created icons as components for easy reuse
    • Applied responsive design for a horizontally elongated card on mobile devices
    • Implemented Skeleton UI on Nation Card and Nation Detail Page
    • Used a custom function to intuitively shorten the population number on Nation Card
    • Applied fade-in-up effect when loading Nation Detail Page
    • Applied scrolling animation to display multiple country names for the respective country on the Nation Detail Page.
  • Rendering Optimization with useDebounce Hook
    • Applied a custom hook to delay search application by 300ms after completion of search term input
  • Load Entire Country Data Based on Scroll
    • Due to the absence of pagination in the REST Countries API, displayed data is split on the client side
    • Globalized search term, option selection information, and data slice count using ContextAPI
    • Ensured that the screen retains the same information (search term, option info, scroll position) even after going back from Nation Detail Page
  • Country Lookup Feature Using Google Maps API
  • Reset Button for Input/Option Initialization Functionality

‼️ To-Do Features

  • Main Layout loads first when the page is initially loaded, causing inconsistency
  • Tooltip display feature
  • Analyze the color code of country images and display the corresponding color as the background
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Lee's solution.

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.