Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 24 days ago

Social links profile using CSS

Ezemaolisaemeka•50
@Ezemaolisaemeka
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 how I was able to complete the layout to closely match the design, especially making it fully responsive using only HTML and CSS. I also liked how I managed the spacing, alignment, and used flexbox to position elements cleanly.

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

One of the main challenges I faced was centering the content vertically and horizontally on the page. At first, I struggled with margin and padding, but I eventually solved it using display: flex with justify-content and align-items to center everything properly.

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

I’d like feedback on how to improve responsiveness, especially for very small or large screens.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • stephany247•730
    @stephany247
    Posted 22 days ago

    Hi Olisa,

    Great work! The layout is clean, well-centered, and your styling is consistent. The hover effect on the buttons is also a nice touch — you're improving steadily! 👏

    ✅ What went well:

    • Good use of Flexbox for layout.
    • Nice contrast and spacing.
    • Button styling and hover effect are on point.

    🔧 What to improve:

    • Missing alt text on the profile image — always include one for accessibility.
    • Use <a> instead of <button> for external links like GitHub, Twitter, etc. It’s more semantic and expected.
    • No need to wrap each button in a <div> — it adds unnecessary markup. You can apply margins directly to the buttons instead.
    • Watch spelling: it’s “LinkedIn”, not “Linkeldn.”
    • Consider adding a custom font like the original design (e.g., "Inter" from Google Fonts).

    Overall, great progress — just clean up the structure a bit, and you’re on your way to writing professional-quality code. 💪✨

  • Egor Pyankov•60
    @egorpya
    Posted 24 days ago

    Hi, good job on the project!

    Several things I want to mention:

    • Do not use <button> tag for links, use <a> instead. Buttons should only be used inside <form> or when a function should be activated.
    • button:hover does not include changing color to grey, as shown in design images.
    a:hover{
      background-color: var(--green-color-from-style-guide);
      color: var(--grey-color-grom-style-guide)
    }
    
    1. You can set border-radius with percentages, like this:
    #avatar{
      border-radius: 50%; /* crops <img> to circle*/
    }
    

    Aside from that, you did a really good job! Keep it up!

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