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

Responsive SocialLink Profile

usman frontend 360•180
@Tech-Badhead
A solution to the Social links profile 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 loved how i tackle the challenge heads on!

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

When i was trying to center the container horizontal and vertical, i was using the the flexbox property but it was not just giving me what i want, however i overcome it with the "display:block" property!

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

When i hover on the social-links link, the hover state moves the whole element and which i guess is not right

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • HassanArafa-dev•250
    @HassanArafa-dev
    Posted 5 months ago

    plus please remove margin and max-width and padding from .container-bg and add min-height: 100vh.

    • and if you need further help please reply to my comment.
    Marked as helpful
  • HassanArafa-dev•250
    @HassanArafa-dev
    Posted 5 months ago

    Hi Usman!, i hope you're doing well.

    • it moves the whole element because you have a 1px border on the element so when you hover it the 1px is being added on the element size, to fix this remove the border on hover and add hsl(75, 94%, 57%) to background instead that should fix it. i wish you the best Usman! keep going you're doing great!
    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

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