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

Made using React and React router

react, react-router
Nikesh W•170
@randomduckduck
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?

Implemented using React router - no page reloads for each link click! Thought would take lots of time, but was a breeze actually.

Also changing css variables using js was new and I feel the possiblities are endless with css-variables and js combo - We can change anything, apply styles to many (even ALL ) elements with just a click. Its cool.

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

flex box related issues. I was trying to make site responsive without using media queries, and spent a lot of time. But media query is made for a reason, and finally used it. took less than 10 mins to make it responsive actually. Right tool for the right job they say. Lesson learned.

Also in previous projects, for changing the border color of inputs when they are in focus I used to change accent-color property. But because this project requires both light and dark view, the limitations of that approach came forth. Then I got to know that there is a property called outline which handles that. Good to know!

What specific areas of your project would you like help with?

No help required for now. I believe all things are done. Thanks

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Purvi Porwal•180
    @purviporwal1812
    Posted 12 months ago

    Antarctica card is not opening (idk if it is domain specific) maybe it could happen with other cards also, you can check once. Ps. I loved the fact that countries are sorted alphabetically.

    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