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

REST Countries API built with Astro

astro, sass/scss, typescript
Younes Atyq•240
@younes-atyq
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 challenges did you encounter, and how did you overcome them?

While tackling this challenge, I made the decision to incorporate Astro’s transitions (morph) to enhance the user experience and give it a more app-like feel. To my surprise, the implementation worked exceptionally well, exceeding my initial expectations. However, this positive experience was limited to a scenario where I was working with a simple dataset that displayed only one region on the screen.

As soon as I attempted to fetch data for all countries, significant issues began to surface. The flickering between light and dark modes took nearly a second to resolve, along with delays in every other feature that relied on client-side JavaScript. In an effort to mitigate these problems, I explored various solutions. Unfortunately, none of my approaches proved effective in handling such a large volume of data.

Realizing that further attempts might lead to diminishing returns, I ultimately decided to remove the transitions altogether. Once I did so, everything functioned smoothly again.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 10 months ago

    Hi Younes Atyq,

    Wow, great job on your project! Your card animation looks fantastic, and your CSS is as good as it gets. It’s impressive to see a project with no noticeable breakpoints. You should definitely be proud of the attention to detail and overall execution.

    One suggestion I have is to add JavaScript transitions to the border buttons. This small enhancement can significantly improve user experience and make a big difference (e.g., changing FRA to France).

    As a little tip, I’d also suggest using a template from Frontend Mentor or another similar resource for your documentation. With the quality of your work, recruiters will definitely appreciate seeing your process and the things you've learned along the way. It can really help showcase your skills and growth.

    Keep up the excellent work!

    Best, Teodor

    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