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

Social links profile solution

Vitor Emanoel da Silva Nogueira•170
@VitorEmanoelNogueira
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tharun Raj•1,330
    @Code-Beaker
    Posted 11 months ago

    Hi there, congratulations on completing this project... You've done a great job on this one! 🎉

    I visited your live site and GitHub repository. And I think you've done a great work trying to match it with the design. I would like to make you aware about some things you can improve in this solution.

    • It will be better for the social links to be marked inside a ul, where each list item is an a inside an li. Something like this:
    <ul class="links">
           <li><a href="#">GitHub</a></li>
           <li><a href="#">Frontend Mentor</a></li>
           ...
    </ul>
    
    • Avoid using id attribute to style elements. They're not meant to be used in CSS but rather in scripting using JavaScript. Here's an article covering this topic.
    • You don't need the strong tag to wrap the link's text. You have to use CSS to style the links.
    • This is a relatively small project and does require a lower number of tags, but in larger projects, you will have lots of components using the same tag but with different looks. It is recommended to use class for all your elements and then style them using their class.
    • Don't limit the width of the body by using width: 100vw because that is completely unnecessary. The body element takes the full width of the document by default. Using a height: 100vh will break the site on taller screens. Instead, use min-height: 100vh and that will fix it.
    • I have noticed that most of your elements use px for padding, margin, font-size, etc.Here's [why font-size should not be in pixels].(https://fedmentor.dev/posts/font-size-px/)
    • To make your CSS cleaner and re-usable, try experimenting with CSS Custom properties/variables

    I hope this helps you improve your solution. These points are important in building better and accessible websites. 😄

    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
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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub