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

github-user-search-app

sass/scss, bem
Kent O'Sullivan•1,870
@12Kentos
A solution to the GitHub user search app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Definitely has some minor bugs, but overall works, took a break last week from coding, and would like to move onto a new project. Will probably come back at some point to finish fleshing it out. I also forgot to make it responsive to mobile... oops.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted almost 3 years ago

    Hello Kent, I do really like how you worked this project. I checked the JavaScript logic noticing the following:

    Line 91 to 132 contains code that could be optimized, I like how you used the .slice() method to get the dates, but the switch structure seems a little bit hardcoded. The create__at string value, can be passed as an argument to a Date object, then the .toLocaleString() method allows you to pull out the values that you specify in different formats and return them as a string value.

     // created_at: '2011-01-25T18:44:36Z'
     let creationDate = new Date(created_at); 
     let joinDate = creationDate.toLocaleString('en-GB', { year: 'numeric', month: 'short', day: 'numeric'});
     // joinDate: '25 Jan 2011'
    

    Good job and I see you around, happpy coding!

    Marked as helpful
  • Jason Moody•300
    @MoodyJW
    Posted about 3 years ago

    Hi Kent! Excellent job on the challenge. I noticed a few issues that might help you improve.

    • definitely take a look at the HTML report, you have a number of accessibility issues regarding missing landmark elements.
    • you have a styling issue in the links section at the bottom, here's a screenshot

    When the text is longer as seen in the image, it's going to force the other elements to the right and it gets a bit sloppy. However, this is pretty easy to fix. There are a lot of ways to handle long strings, but my favorite is to just truncate and add an ellipsis.

    On the container div, the links wrapper, add overflow: hidden to your sass. Then on the p element, add overflow: hidden; width: 100%; text-overflow: ellipsis. That's it!

    The icons are also a bit clipped, but that's also easy enough to fix! If you open the svg file for the icon, there should be a width and height. Simply set the same width and height on the container div and it should be perfect.

    Great job, keep it up!

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub