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

Social links profile using HTML & CSS

mamman-naf•130
@mamman-naf
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 AM VERY CONFIDENT THAT I DID GOOD ON THIS PROJECT. AND WOULD WANT TO BETTER UNDERSTAND THE FLEX BOX PROPERTY.

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

SIZING THE DIVS (HEIGHT AND WIDTH)WERE VERY CHALLENGING FOR ME.

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

THE FLEX-BOX PART AND SIZING UNITS.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dominic•170
    @Dpal88
    Posted 9 months ago

    Hi @mamman-naf! Great work on completing this challenge, and your design is spot on!

    As far as sizing units go, it really depends on the situation. For font size I would recommend using rem units. Rem units are a relative length unit which just means that they are relative to something else, in this case rem units are relative to the font size of the root element. This means that 1rem is equal to the font size of the html element, which for most browsers the default is 16px. Whereas px units are an absolute length unit, meaning that their size will not change. The nice part about using rem units is that when users change the default font size in their browser the text will scale accordingly.

    Also I noticed that you were using percentages for your margins, and I would recommend using rem units instead for margin and padding.

    All the different units can make things a little confusing but the more you work with these different units the easier it will become. Also flexbox is a great and essential tool to learn, I wont get into here because it's a lot to explain but I'll link some helpful resources down below.

    https://css-tricks.com/snippets/css/a-guide-to-flexbox/ https://www.youtube.com/watch?v=GteJWhCikCk

    I hope this helps and if you have any questions feel free to reach out.

    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