Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

REST Countries API | LocalStorage | Theme Switch | Vanilla JS | SCSS

Folarin Akinloye•1,240
@folathecoder
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


Hi Devs! 😎

It has been a while since I published a new challenge. I have been learning JavaScript full-time and I just completed an internship program (I was the frontend team-lead 😎).

This challenge was very fun to execute. The challenge helped me master how to effectively consume API.

Kindly explore my solution and leave a feedback!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • John•250
    @JohnBroers
    Posted almost 4 years ago

    Nice work Folarin! Nice addition of the hover animation on the country blocks. A couple remarks and improvements from my side:

    1. The country blocks in the overview feel a little bit messy because of the different heights and sizes:
    • I would suggest setting a suitable fixed height on the flag images.
    • Make the flex items 'align-self: stretch' so all items in a row are equal height.
    1. I feel like the font-family is different then the design. Maybe that's design choice of your own. But be sure to set a font-family on the input and select elements because those ones are using the default browser font right now.

    2. Try to add thousand separators to the population numbers to make them more readable. (So 27,657,145 instead of 27657145)

    3. The country detail page keeps showing a loading spinner at the bottom. Even though i feel like everything has been loaded.

    4. I noticed a lot of console.logs when i used the search function. You might wanna remove that when you clean up your code.

    Your javascript code looks really well structured, nice job!

    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