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

Responsive card with social link buttons

Gregor de Cillia•190
@GregorDeCillia
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I am still not sure what the right strategy for the responsive card width/padding is. It seems to match up in the sizes from the designs but there might be a more elegant way (with clamp?) for those two properties.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ashish Kumar•150
    @0KAshish
    Posted about 2 months ago

    Hello there 👋. Great job on building the Social Links Profile card!

    You've done well applying layout and styling principles. Here's a quick review with some suggestions to improve your code:


    • 🎯 Layout & Structure:
      Your use of Flexbox and the centered .card layout is solid! Using margin: auto with a flex parent is a great way to center elements vertically.

    • ✨ Styling:
      The color palette and hover effects are on point and responsive design is nicely handled with the media query. Great job using :root for design tokens!


    🛠 Suggestions for improvement:

    • 🔁 Use semantic HTML:
      Consider using <a> tags for the social links instead of <button>. These are links to external sites, so semantically, anchor tags are more appropriate.

    • 🧹 Clean up unused rules:
      Currently, all buttons are <button> elements but are functioning as links. Also, you may want to remove or rework the .attribution absolute positioning if it causes overlap in smaller viewports.

    • 📱 Mobile tweaks:
      You already have responsive padding on the card — nice! Just ensure that the layout doesn’t get too squished on smaller devices (e.g., padding around buttons can be reduced slightly if needed).


    Overall, this is a clean and solid solution. With just a few semantic improvements, it’ll be even better! 🚀

    Happy coding! 😊

    Marked as helpful
  • friedmantech•100
    @friedmantech
    Posted 2 months ago

    Great work, just the footer is stuck in the bottom left - its size seems to be limited to its text and is therefore not centering...

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

Oops! 😬

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

Log in with GitHub