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

social links card using html and css (flexbox and grid)

T Moses•150
@Andrew-003
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

  • LelloX-Dev•110
    @LelloX-Dev
    Posted about 2 months ago

    ✅ What’s Working Well

    1. Layout & Structure body using display: grid with align-items: center is a clean and effective way to vertically center content. ✅

    .container uses flex with flex-direction: column and align-items: center, which works well for stacking profile content. ✅

    1. Responsiveness You’ve kept widths relative (rem units) and used margin-left/right: auto for centering, which supports responsive design. ✅

    2. Border Radius & Spacing Use of border-radius (2ch, 3rem) adds nice rounded visuals.

    Padding and margin usage is generally well-balanced.

    1. Hover Effects .socials :hover changes background and text color, providing a clear visual cue. ✅

    ❌ What Needs Improvement

    1. Color Palette You're using custom rgba() values instead of the specified colors from the style guide. Replace with the following for consistency:

    ✅ Replace rgba(4, 4, 4, 0.95) with hsl(0, 0%, 8%) (--Grey-900)

    ✅ Replace rgba(22, 22, 22, 0.9) with hsl(0, 0%, 12%) (--Grey-800)

    ✅ Replace rgba(46, 46, 46, 0.8) with hsl(0, 0%, 20%) (--Grey-700)

    ✅ Replace rgb(129, 220, 38) with hsl(75, 94%, 57%) (the official Green)

    1. Typography You’re using Arial, Helvetica, sans-serif, but the challenge specifies the Inter font family.

    ❗ Replace with:

    css Copia Modifica font-family: "Inter", sans-serif; Set a base font-size: 14px in the body to align with the style guide.

    1. Selector Issues .socials :hover has a space, meaning it targets any element inside .socials on hover. This could lead to unexpected behavior.

    ✅ Change to .socials a:hover for correct targeting.

    1. Code Consistency / Cleanup Some redundancy in margin-right: auto; margin-left: auto; inside .container, which is already horizontally centering via flexbox and width.

    Consider grouping shared font-family rules to avoid repetition.

    💡 Suggestions for Enhancement Add media queries for smaller viewports (320px–375px) to truly meet the design spec and be mobile-friendly.

    Consider using CSS variables (--color-name) for the color palette to improve maintainability and theming.

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