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

Social Links (HTML/CSS)

Ki'ara Colbert•130
@kiaraaa123
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I'm having trouble with the margins for the profile image. I've made it a block element, which allows me to center it, but then removes the top margin. Any help would be appreciated. Thanks! :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rowan Pereira•330
    @rowanrooster
    Posted 12 months ago

    Try using padding on the .card element instead of margin. But, i think if you add even 1px of padding you should start seeing the margins - this is because of margin collapse / stacking margins.

    if im right, check this article for more on stacking margins: FreeCodeCamp

    Hope that helps, but good work! Clean code and I like the comments in the css!

    Marked as helpful
  • Alberto José•630
    @alberto-rj
    Posted 12 months ago

    👋 Hello @kiaraaa123!

    👏 Congrats on investing your time and taking your frontend skills to the next level with the Social links profile challenge.

    I have a few suggestions that could help you improve your solution to this challenge.

    On line 34 to 38 of your index.html file: A p element does not have to be directly a child of a in this case, instead you could:

    • Add a title for your unordered list (the title should be visually hidden, as per the design, it should only be available to screen reader users)
    • Create an unordered list with a ul
    • Put each a inside an li (and each li inside the ul created)

    Note: It is recommended to do this, because in this case you have a group of links of the same kind, "your social networks".

    Useful resources:

    • The anatomy of visually-hidden
    • <ul>: The Unordered List element

    Good practices for your styles.css file:

    Avoid using the unit px in your properties. Instead, use the rem unit. This will make the layout scale correctly for people who have a different text size setting. To demonstrate go into your browser settings and change the text size to a larger value like 32px — currently your solution would still be really narrow for those people. But if you use rem it would adjust.

    Note: The px unit is generally recommended more in the border and box-shadow properties, because these properties do not change in relation to the text size.

    Useful resources:

    • PX or REM in CSS? Just Use REM

    Keep learning, coding and sharing! 🌟

    Happy coding! 🚀

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