Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Responsive rest-countries app

next, tanstack-query, typescript, tailwind-css
Oladayo Ajibola•80
@DeeBabaTech
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?

The project was overall nice. I was able to conclude all requested features. Feel free to give comments.

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

No challenge actually.

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

None for now.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Thomas TS•1,270
    @ttsoares
    Posted about 1 month ago

    Neat solution !

    An UX suggestion:

    If the page is in dark mode, it makes more sense if the upper corner show “Light Mode” and vice versa. When the user click in the mode toggler button is to change to the other mode not the present one.

    Comments:

    • Usually we do not leave unnecessary comments in the final version. Like the one in the tailwind.config.js.
    • Your "Back" button is moving back in the browsers's history. When I did this solution, it was my understanding that this button move the user back to the all flags page.
    Marked as helpful
  • Marzia Jalili•7,190
    @MarziaJalili
    Posted about 1 month ago

    A game build! 👑

    A tiny tweak?

    ✅ Consider using the label element for the entire input section so that clicking anywhere on the box will take you to the input field.

    Other than that, the web's lit! 🔥🔥🔥

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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