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

REST-Countries-API-with-color-theme-switcher-v2-Redux-Tailwind

react, redux-toolkit, vite, tailwind-css
Teodor Jenkler•4,040
@TedJenkler
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'm really proud of the progress I've made over the past eight months. Reflecting on where I started, it's amazing to see how much I've improved. This project showcases my growth and hard work. I'm excited to see where I'll be in another eight months!

For future updates, I plan to:

Play with Animations: Incorporate animations for cards and hover effects to enhance user interaction and visual appeal.

Refine Details: Focus on improving spacing, alignment, and overall visual consistency to create a more polished and cohesive user experience.

Optimize Data Fetching: Consider fetching all data once and then filtering it locally to reduce the number of API calls. I'm still exploring the best method for this approach and if it would be better.

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

Honestly, the biggest challenge was trying to finish this over a weekend. Maybe the real challenge should be getting more sleep, but well, well. On the bright side, I significantly improved my grid skills with this project!

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

I'd love to hear your thoughts on:

Fetch and Search Functionality: Is fetching all data once and filtering locally a better approach, or should I stick with fetching data on demand?

Responsiveness: I chose a growing approach for responsiveness because it looked better than having a single item in the middle on small tablets. Do you think this approach works well, or do you have suggestions for improvement?

Your feedback will help me refine and improve the project. Thank you!

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 Teodor Jenkler'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.