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

Social links profile

arthurquique•50
@arthurquique
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 think I have a prettier code than on the last project where I used divs for everything.

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

Getting started is always the most challenging to me but it becomes more and more easy with experience.

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

Tips for judging which type of display to use for each element.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Gabe•320
    @gabei
    Posted 4 months ago

    Nice job! A few things to mention, and hopefully an answer to your question.

    1. As far as types of display go, I think you're fine. One thing I would consider is the type of elements you use for the social links on the card. They might be thought of as an unordered list, which is helpful to screen readers when announcing the content ahead. Styling the section as a grid works fine in your case, but I think beginning with a list of links here makes the overall styling a bit simpler in the long run.

    2. Check out how 100vh on the body affects the card's visibility when you switch to landscape mode on a mobile device. This can actually be a quick fix (check out the min-height property, for example).

    Hope this helps. Happy coding!

    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