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

REST Countries API with colour theme switcher using NextJS

next, tailwind-css, typescript
Mirror83•200
@Mirror83
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 am most proud of the theme switcher, but that is also the thing that I would do differently.

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

The initial approach I used to change the theme worked, but since the server does not know the theme saved at the client's computer, there was a jarring theme change on initial page load. I fixed this by making the children of the root layout to be client components. However, (to me) this was more of an acceptable compromise than a solution to the challenge as it also brings its own issues...

After the server payload reaches the client, an empty white page is displayed as the theme is loaded and any server functions are run before the full page is loaded with the correct theme.

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

I would like to know of better ways of handling theme changes in Next.js using TailwindCSS.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hi Mirror83,

    Your project is looking fantastic! I can see you've put a lot of effort into it, and it's shaping up really well.

    Regarding handling theme changes in Next.js with TailwindCSS, I can't share specific best practices since I primarily use React and Redux. However, one small tip that could make your project stand out is to create a custom select component. It can significantly enhance the user experience and give your project a unique touch.

    I'm making a remake of this project myself and still haven't decided whether to use the first card scale until it fits two columns or make it like yours and have it in the middle. Your result is actually looking really smooth and works well on both large screens and 320px, so you definitely have an eye for details.

    Keep up the great work!

    Best, Ted

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