Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

REST Countries API

accessibility, fetch, lit
P
Aydan•680
@AydanKara
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)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • BrunoMoleta•700
    @brunomoleta
    Posted about 1 year ago

    Hallo Aydan,

    I cloned your project locally to see it closely and give you a more precise feedback.

    It took a while to understand the project's code, as the files are long and accomplish multiple things.

    For example, the details.js file has the HTML component and the function that fetches a country's info. Try to make each separate so it's easier for people to read your code and contribute.

    The same goes for creating a file for the dark mode handler, separating the function from the header component.

    Also, it would be more performant to make several API requests so that we don't end up with a large object containing all the countries. And perhaps the landing page could fetch a few random ones instead of every country.

    And when filtering the continent, there would be a new fetch request to the back end, not a filter at the large object.

    About the CSS, I noticed you used object-fit: cover at the flags. Perhaps that's not the best alternative because there is no "cropped flag".

    So you may be better off using object-fit: contain with a background behind the flag to distinguish the background of the app from the one of the cards.

    Also, the div you used to handle the dark mode should be a button. In this case, the Tab key would be available.

          <div id="color-switcher">
            <i class="bx bx-moon" id="icon"></i>
            <span id="mode" @click=${onModeChange}>Dark Mode</span>
          </div>
    

    I also advise you to test different font sizes on the browser, as components got very large on my screen. In my local environment, I use a default font size of 24px. I imagine you tested locally with a smaller font, and things looked ok, but the components here got disorganized, and the layout misplaced.

    If you are interested in learning about suiting different font sizes better, please check this post from [Josh Comeau] (https://www.joshwcomeau.com/css/surprising-truth-about-pixels-and-accessibility/) :)

    You did a terrific job using 'id' frequently in the tags. It makes life easier for people who test it. So I suggest you keep doing so :)

    Keep up the great effort Aydan.

    I'm sure that you are a better programmer since the time you did this project, but I got interested in reviewing it for it is a nice challenge.

    Best regards from Brazil, Bruno

    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