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

rest-countries

node, react, styled-components, typescript, mongodb
Oleksandr•690
@Oleksandr-Berd
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


🌍 Just Completed a Country Explorer App! 🌎

Exciting news! I've just wrapped up a new project that I'm really proud of: a Country Explorer App. 🚀

This project was a fantastic opportunity for me to put my React, styled-components, TypeScript, Node.js, and MongoDB skills to the test. The main goal was to integrate with the REST Countries API and create a sleek and user-friendly platform for exploring country information.

📌 Here's what the app allows users to do:

Browse Countries: The homepage provides a comprehensive list of countries sourced directly from the REST Countries API.

Search and Filter: Users can search for specific countries using a convenient search input. Moreover, I've implemented a region filter to help users sort countries by region.

Country Details: Clicking on a country opens a detailed information page that showcases key data about the selected country, such as its population, capital, languages, and more.

Dark Mode: As a bonus challenge, I implemented a toggle for light and dark modes, enhancing user experience and accessibility.

The app's design adheres to a style guide that's been thoughtfully created, ensuring a seamless and visually pleasing experience for users. The technologies I chose allowed me to build a responsive and performant application that functions smoothly on various devices.

I want to express my gratitude to the REST Countries API for providing the valuable data that powers this app.

I'm incredibly excited to have completed this project, and I'm looking forward to tackling more challenges that help me refine my development skills. If you have any questions, feedback, or just want to chat about tech, feel free to reach out. Let's continue building amazing things together! 💻🌐🚀

#CountryExplorerApp #React #styledcomponents #TypeScript #Nodejs #MongoDB #WebDevelopment

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Oleksandr'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.