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

🚀 Github users Search [Axios] [GSAP] [TailwindCSS]🚀

axios, tailwind-css, gsap
Zsolt Varjú•490
@zsoltvarju
A solution to the GitHub user search app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Everyone!!!

My approach for the project:

During the development of this app, I learned and practiced a lot while using APIs.

  • I used the Axios library to interact with the API, which became increasingly familiar to me.
  • I was introduced to a new application called Postman, which I used to analyze the API data.
  • I added some error handling with a callback and a counter that triggers if the user is not found or when there are too many API requests in a short time.
  • This was also my first project where I implemented dark and light themes. It was fun learning about this feature, and I added a script to check the base theme settings of the user and use a color palette according to the user's preference.
  • Additionally, this was my first project using Tailwind CSS. Initially, it was overwhelming, but as I neared the end of this project, it became easier to use. I really like it and definitely plan to use it in future projects. I see a greater advantage of using it in React, where components are used, because in a simple HTML website like this, the large number of class names can be a bit overwhelming.
  • In the end, I also used GSAP to animate everything and used JavaScript modules for the first time to import animation functions from the animations.js file to my ApiHandler.js file.

There is an interresting error which i dont udnerstand and would be more then happy if someone could help:

  • In chrome the text at the twitter logo is not visible. It gets an display: none !important from the users stylesheet, in edge and firefox it works fine for me but in chrome it does not.

Verdict:

There is plenty of room for improvement in this project. One aspect that could enhance its appearance is implementing a real-time search as the user types in a name. I definitely want to try that, but I need to consider implementing a function to prevent excessive API requests with every keystroke. Additionally, more error checks and a test file to verify functionality would be beneficial. I may add these features later as well.

Overall, I really liked this project. It was challenging but also fun, and I learned a lot from it.

Have a great day and happy coding :)

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 Zsolt Varjú'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.