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

Social Links Profile

Riccardo•20
@ricky0709
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?

Im proud that i was able to recreate this project, since I've done it all by myself

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

Had a problem in loading the fonts and using the border-radius element

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

fonts

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • MEHNOOR SHAHBAZ•720
    @Mahnoor366880
    Posted 4 months ago

    Hey ricky , great effort on your project! It’s very close to the required results, and with a few refinements, you can make it a perfect match. Here’s what you can improve:

    1. Card Size & Positioning

    Your project has a slightly larger card than the required results. Try reducing its width to match the second image.

    Ensure the card is centered properly for a balanced look.

    1. Button Styling

    In your project, the buttons are wider compared to the required results. Adjust their width to be more compact.

    The spacing between buttons in your project is slightly off—reduce the gaps to match the required results.

    1. Typography & Alignment

    In your project, the text inside the buttons appears slightly misaligned. Adjust the vertical alignment for a cleaner look.

    Ensure the font size, weight, and spacing of the name, location, and bio text match the required results.

    1. Card Border & Styling

    Your project has slightly more rounded corners. Adjust the border-radius to match the required results.

    Your project is already looking great! Just these small refinements, and it will perfectly match the required results. Keep up the amazing work! 🚀

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