Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

Rest countries API with colour theme switcher master Solution

Chinmay Agarwal•235
@chinmayagarwal3007
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


Hello 👋!

Worked really hard on this one, would really appreciate if you guys can give some feedback.🤓.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mojtaba Mosavi•3,740
    @MojtabaMosavi
    Posted about 3 years ago

    Good job, I working on this one as well. Take a look at the following points:

    • In my opinion the more interactive a UI is the better and therefor as frontend dev you should use at every at you disposal where it makes sence for example for simple link a hover state suffices but somewhere else you might wanna spice things up with custom animation/transitions.

      1. the toggle button for the theme needs a hover state to communicate to the users it could be changed.

      2. the card representing each contry needs a hover state as well to let the user know there is more.

      3. The border contries displayed in the footer of when you click on contry

    • Take a look at the issu rapport generated and correct them.

    • The mode toggle button is not keybord accessible and has a too wide of a clickable area by which I mean if you click in the middle of header you can change the theme, the clickable area should be a small rectangle covering the toggle button.

    • The queries that don't mapp to a real country, it should display a "no result" message to let the user know it does not exist.

    Happy coding :=)

    Marked as helpful
  • Travolgi 🍕•31,300
    @denielden
    Posted about 3 years ago

    Hi Chinmay, great work on this challenge! 😉

    Here are a few tips for improve your code:

    • add <title> to head of document
    • add header tag and wrap the navbar for improve the Accessibility
    • add main tag and wrap the cards for improve the Accessibility
    • img element must have an alt attribute, it's very important!
    • remove all unnecessary code, the less you write the better as well as being clearer: for example the div container of images of flag and html comments
    • use h2 for the name country into the card
    • you can use ul element instead multiple p for the text details of country
    • if I type a query that doesn't give any results, nothing happens, try adding a "no results" message
    • I would also add a query reset button, I find it very convenient

    Overall you did well 😁 Hope this help!

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub