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

Social Links Profile

P
bsd-rgb•110
@bsd-rgb
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I had challenges with the button placement. I had to mess around with the flexbox properties in order to get it to look like the design.

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

Any tips suggestions on getting the button placement. Is flexbox the best solution for this?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ayokanmi Adejola•1,490
    @Ayokanmi-Adejola
    Posted 2 months ago

    I've had a look at your Social Links Profile solution, and it's really well done! You've captured the design effectively and created a clean, functional component.

    What I Liked :

    • Accurate Design Implementation: The visual design, colors, typography, and overall appearance of the card are very true to the Frontend Mentor challenge.
    • Excellent Responsiveness: The card adapts perfectly to different screen sizes, remaining well-proportioned and readable on both desktop and mobile.
    • Clean and Organized Layout: The content within the card is well-spaced and easy to digest.

    Addressing Your Challenges (Button Placement):

    You mentioned having challenges with button placement using Flexbox and asked if Flexbox is the best solution.

    • Yes, Flexbox is absolutely a fantastic solution for this! For arranging a stack of items like your social links, it's often the most straightforward and powerful tool.
    • Tips for Button Placement with Flexbox:
      • For the parent container of your buttons (e.g., a div wrapping all the links), you would typically set:
        display: flex;
        flex-direction: column; /* To stack them vertically */
        align-items: center;   /* To center them horizontally within the card */
        gap: 15px;             /* Or whatever spacing you need between buttons */
        
      • Then, for the individual button/link elements themselves, to make them span the full available width (as per the design), you can set:
        width: 100%;
        /* You might also need max-width if the card itself has a max-width */
        
      • This combination on the parent and children is a very common and effective way to achieve vertically stacked, horizontally centered elements that span full width. It seems like you figured out a great solution, and this pattern is likely what you experimented with!

    Areas for General Improvement :

    1. HTML Semantics:

      • The "Social Links Profile" is likely a standalone component. Ensure the main name (e.g., "Jessica Randall") is wrapped in an <h1> tag if it's the primary heading within the component's context, or an <h2> if the component is part of a larger page.
      • For the social links themselves, it's best practice to use an unordered list (<ul> and <li>) where each list item contains an <a> tag for the link. This provides better semantic structure for navigation and accessibility.
    2. Accessibility:

      • Ensure your profile image has a descriptive alt attribute (e.g., alt="Jessica Randall's profile picture"). This is crucial for screen reader users.
      • All interactive elements (your social links) should have clear visual focus indicators when navigated to using a keyboard (Tab key). The default browser outline usually works well, but you can style it for better visual appeal while ensuring it's always present.
    3. CSS Best Practices:

      • Consider using CSS Variables (Custom Properties) for your colors, font sizes, and common spacing values. This makes your stylesheet more maintainable, easier to update, and ensures consistency throughout the project.

    In Summary:
    
    This is a fantastic Social Links Profile, You've done an excellent job with the design, responsiveness, and it's great that you tackled the button placement with Flexbox – you were definitely on the right track as it's a powerful tool for this. Focusing on these semantic HTML and accessibility refinements will make your solution even more robust and user-friendly.
    
    Keep up the fantastic work!
    
    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