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

Responsive Social Links Profile

Catarina Rodrigues•20
@CatRod
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 love that I could personalize it with my own links.

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

The most challenging thing was to change the underline effect, because I nested a div inside the link 😅

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

I'd like to know your sincere opinion of what would you do differently!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Steven Stroud•11,890
    @Stroudy
    Posted 11 months ago

    Hey, Great job with this solution you should be proud, A few things I noticed,

    • Missing a <meta> description tag for SEO purposes,
    • Setting a height and I can see you have added a width attribute to your <img> This will increase performance to reduce layout shifts and improve CLS, It reserves the space on the page for the image,
    • It is best practice to have a <main> tag inside your body highlighting the main section.
    • Links rely on colour to be distinguishable, This applies to your .attribution, Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision.
    • ‍Using max-width: 100% or min-width: 100% is way more responsive then just width:100%, check out this article also from the same Frontend mentor dev responsive-meaning, she goes into more detail.
    • You should avoid using px as it is an absolute unit and not a responsive unit like rem or em, You should look at this article from a Frontend mentor dev, Why font-size must NEVER be in pixels.
    • Another great resource for px to rem converter.
    • @media should also be in relative units like rem or em,
    • You should apply a full modern reset to make things easier as you build, check out this site for a Full modern reset
    • Using a naming convention like BEM, Using proper naming will prepare you for the changes in design of the website.
    • It is best practice to use margin-inline: auto; to center left and right then than just margin: auto;, You can center the height by using this code snippet
      min-height: 100svh;
      display: flex;
      justify-content: center;
      flex-direction: column;
    

    I hope you found some of this information helpful, You should give the articles a good read and I look forward to seeing some more from you, Happy coding! 💻

    Marked as helpful
  • P
    Nico•330
    @Nico243
    Posted 11 months ago

    When adjusting an image we always use width and height

    img { height: 80px; width: 80px; border-radius: 50%; }

    You must take the following out of your HTML as it's making an oval:

    width="200px"

    Your image should look great now!

    Let me know if you need more help, this is great practice for me!

    Marked as helpful
  • P
    Nico•330
    @Nico243
    Posted 11 months ago

    First off! It looks great I have a few suggestions that might be of interest.

    You said you fixed the <h2> </h3>, It didn't appear to have changed on your code.

    It could be of the following reason:

    When we make changes on our code in VSC it doesn't update on our live page automatically so we have to do it manually on VSC's terminal

    You could achieve this with the following steps.

    1. git status (You'll see files in the color of red, this mean it's new changes)
    2. git add . (This adds all files, be careful not to add files your not suppose to)
    3. git commit -m "Updated HTML (or relevant changes)"
    4. git push origin main

    your new files/updates should be uploaded to the internet now. It takes about 30 - 40 seconds before you'll see any changes.

    happy coding

    Marked as helpful
  • P
    Nico•330
    @Nico243
    Posted 11 months ago
    1. If you have a figma account you can create a new file
    2. Then select import
    3. You want to go to your social-links-profile-figma
    4. open the social-links-profile.fig file

    This would import all the details that you need with color coding and sizes which makes it easier to navigate through.

    This is going to be helpful the further you go along with this course

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

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