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

REST countries api

Duyen Nguyen•950
@Duyen-codes
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


I'm stuck with showing the modal when any country card gets clicked. Could anyone please shine some lights. Thanks a lot.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted about 3 years ago

    Hey good job completing this challenge.

    Keep up the good work

    Your solution looks great however I think that for the dark theme the card title and description should be white for easier readibility

    In terms of accessibility issues simply wrap all your content between main tags

    In terms of validation errors, attribute href not allowed on element div at this point, this means that the div element has no href attribute

    I hope this helps

    Cheers Happy coding 👍

    Marked as helpful
  • Prabhash Ranjan•2,540
    @besttlookk
    Posted about 3 years ago

    Hi,

    After looking into your solution, i found out a lot of but which i would like to point it out. 1.In light mode, there is no contrast in both filter and search w.r.t background. Try adding some shadow. 2. Somehow i am not able to click on individual country card to see its detail. I wonder if you have implemented it or not. 3.Are you making a new network for filtering and search?? why bother if you already have all the countries list during initail load. Filter through that only. 4. I would also love to see some hover effect on cards to make it interactive. 5. Also give some max-width for the content area. On wide screen it spread all over the screen , which dows not look good(in my opinion).

    I am no expert but happy to help if you need any help. let me know.

    Also, here is my solution: https://rest-countries-fem-v2.herokuapp.com/

    Do let me know if you find any bug in mine.

    Good Luck, #happyCoding

    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