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

REST Countries Dashboard built with HTML | CSS | JS | REACT - MikDra1

react, styled-components, vite, react-router
P
MikDra1•7,450
@MikDra1
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?

💻 Hello, Frontend Mentor Community,

This is my solution for the REST Countries API.

  • Scored 99,25% on Google Pagespeed Insights! 🚀
  • Solution with 100% W3C validation accuracy 🌟
  • You can switch from white to black and from black to white theme. 💡
  • You can filter the number of countries that you want at the same time on the page. 🔢
  • You can check bordering countries just by clicking on them in the country detail ⛺
  • I've implemented a pagination for your better experience so that you don't have 250 results at one page. 📃

🛠️ Built with:

  1. HTML ✨
  2. CSS 🎨
  3. JavaScript 🧾
  4. React ⚛️
  5. Vite.js 💡
  6. Context API 🛒
  7. Styled-Components 💅
  • Fully responsive design crafted with a mobile-first approach 📲

  • Enjoyed every moment coding this! 😎

  • Feedback is always welcome—let’s grow together! 🌱

  • Completed 1 out of 3 Advanced Challenges so far—keeping up the momentum! 🔥

  • 👨‍💻 Join me on my coding journey as I tackle advanced challenges and add innovative touches to every project.

  • As I am developing in my journey with React I'm really looking forward to hearing your thoughts and suggestions! 💡

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 MikDra1'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.