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

Social link profile using HTML and CSS

𝓛𝓮𝓸𝓼𝓶𝓪𝓻𝓽•80
@leo-smart7
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?

Really enjoyed working on this project, it helped me test out level on CSS.

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

I encountered a bit challenge during the creation of the social link buttons, I had to make research to figure how to get it done.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bello Ibrahim•660
    @repro123
    Posted 6 months ago

    Well done on completing the challenge. Just a few observations:

    • Make sure you start each project in a different folder, don't put all your projects in one folder

    • Use the DRY (Don't Repeat Yourself) principle in your CSS. You have many margin: 0; and padding: 0; in multiple places. You can use:

    * {
    margin: 0;
    padding: 0;
    }
    
    • brings me to my third point. Try and use a modern CSS reset before your styles in your CSS file. Check out Andy Bell or Josh Comeau's CSS resets

    • there are too many combinators. Using just a CSS class will be fine.

    • avoid using px for font size or for media query. It's bad for responsives.

    Nice job, once more

    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

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