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

Social Links Profile using HTML and CSS

Dylan Molthu•70
@dmolthu
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'm most proud of my CSS skills developing and my understanding of certain properties is increasing. The thing that I would do differently is finding out ways to simplify my code because there probably are plenty of lines that might not have to be there.

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

I encountered a few challenges with spacing some elements out on the screen, like the location paragraph from the bio paragraph. I figured it out by just playing around with the spacing with some of the elements parent elements and also using the margin property to space them out from the top.

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

I would like help with getting a better understanding of spacing and how I could simplify my code by making better use of group selectors and finding out what some of the default values are to some properties.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • amina-refik•80
    @amina-refik
    Posted about 1 year ago

    Hello Dylan,

    I hope you're having a great learning experience.

    Overall, your solution looks quite similar, but it seems to have issues with responsiveness.

    As you can observe from this screenshot, when I adjusted the window size, the layout broke. This could be attributed to two main reasons you should consider:

    1. Absolute Positioning: Using position: absolute disrupts the flow of your document. Typically, you would use absolute positioning if you don't need to worry about elements overlapping.

    2. Percentage vs. Fixed Dimensions: When a parent element uses a percentage for sizing and its children use fixed dimensions, overflow issues can arise as the screen size decreases. You can address this by either hiding the overflow or adding a scrollbar if you prefer not to alter the dimensions of the child elements.

    The simplest fix I suggest (although you could explore alternative approaches) is to change the height of the card to a fixed dimension. This adjustment should resolve the overlap issue, as demonstrated in this screenshot:

    .sec-1 {
      height: 620px;
    }
    

    Regarding spacing, I recommend using the design image as a background and reducing the opacity of your main element and try to align them as closely as possible.

    Lastly, don't forget to include the page icon.

    I apologize if my feedback seems lengthy, but I hope it proves helpful. Happy coding!

    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