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

GitHub User Search

sass/scss
AceDub•250
@AceDub
A solution to the GitHub user search app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My first time working with an API. Would appreciate any feedback or criticism.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hi, AceDub! 👋

    Congratulations on completing this challenge! 🎉 Your solution looks pretty good! 😀 I like the idea of having a loading spinner! 👍

    Here are some suggestions for improvements.

    • I recommend adding rel="noopener" to any anchor tags that have target="_blank". This is a security essential for external links. I suggest reading the web.dev article to learn more about this.
    • I would not recommend setting any height to the html element. I suggest treating the body element as the webpage of the site.
    • I would also suggest not setting any height to the body element. If you ever need to set a height then use min-height instead. This way, the body element is allowed to grow if ever needed.
    • Having the desktop layout at 1440px is too late. So, I suggest adjusting the breakpoint of the media query. As a side note, the design sizes are telling you that the site should look like this at this specific screen size. They have nothing to do with the media queries.
    • The statistic should be a list with three bullet points. Also, the statistic categories and the statistic numbers should not be headings. Use span instead (since it will be wrapped by li). Heading tags have meaning and are used to give structure to the page. You can think of headings like titles in documents. So, I recommend writing the HTML without any styling so that you can make a better decision on what HTML element you should use for the web content.

    Overall, great work. The site even still looks good at 320px which I would consider the smallest screen size.

    I hope this helps! Keep up the good work! 👍

  • mubizzy•1,520
    @mubizzy
    Posted about 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

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

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.