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

Countries API Project - Angular, Tailwind, Typescript

angular, typescript, tailwind-css
Juan A Lagunas Palomares•430
@dev-jLagunas
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 are you most proud of, and what would you do differently next time?

I am proud that I was able to work Angular and Tailwind again! I was pretty rusty with both of them so this project took me longer than expected. I am also excited that I finally am starting to understand rxjs observables and subjects. I can understand how they are used and how useful they are much more now!

Thoughts I love the speed and the granular control Tailwind CSS gives me but it did feel strange filling my html with a huge number of classes. It also felt less natural now that I have a stronger grasp on SCSS. Nonetheless, Tailwind is awesome and I look forward to using it again!

What challenges did you encounter, and how did you overcome them?

This project was deceptively tricky. I encountered small minor annoyances when trying to find the proper layout to match the design requirements. This also forced me to use more tags than I felt comfortable with. I don't think I kept the best practices in regards to semantic HTML and accessibility so I need to be careful with this for next time.

Also, there were a lot more instances where I needed to access the API data, manipulate it, and display it, than I realized at first. Luckily rxjs came to the rescue here so data manipulation and state management was straightforward.

What specific areas of your project would you like help with?

Not so much help, but I am curious as to why not very many people here use Angular? I know its a bit stuffed for lighter projects such as these, but I find myself quite enjoying working with Angular!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Juan A Lagunas Palomares's solution.

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.