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

repsonsive social media links using flex , hover event

pure-css
Sarobidy•50
@ravaka5
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted 5 months ago

    Hi @ravaka5,

    I hope you're doing well! Here are a few suggestions to improve the structure and alignment of your code:

    1. Use ul and li for Links:
      Since these links represent a list of social media profiles, it's semantically better to wrap them in an unordered list (<ul>) and list items (<li>), instead of using <div>. This will improve accessibility and readability for both developers and screen readers.

      Example:

      <ul class="social-links">
        <li><a href="https://github.com/ravaka5">GitHub</a></li>
        <li><a href="https://www.frontendmentor.io/profile/ravaka5">Frontend Mentor</a></li>
        <li><a href="https://www.linkedin.com/in/ravaka-ramarojaona-145355249/">LinkedIn</a></li>
        <li><a href="https://x.com/RavakaRama33850">Twitter</a></li>
        <li><a href="https://www.instagram.com/ravaka_nyaina_sarobidy/">Instagram</a></li>
      </ul>
      
    2. Centering Your Card:
      To center your card vertically and horizontally on the screen, make the following tweaks to your CSS for a cleaner layout:

      • Add min-height to ensure the body takes the full height of the viewport:

        body {
          background-color: hsl(0, 0%, 8%);
          display: flex;
          flex-direction: column;
          justify-content: center;
          align-items: center;
          color: white;
          min-height: 100vh; /* Ensures body takes full viewport height */
        }
        
      • Remove the position: fixed; from the footer as it's unnecessary for centering:

        footer {
          text-align: center;
          width: 100%;
        }
        
      • Finally, remove the margin-top in the main tag to prevent unnecessary spacing:

        main {
          padding: 32px 24px;
          background: hsl(0, 0%, 12%);
          border-radius: 14px;
        }
        

    These small adjustments will help enhance your layout and make your code more semantic. Keep up the great work! 👍

    Let me know if you need further help!

  • Marzia Jalili•7,650
    @MarziaJalili
    Posted 5 months ago

    Great job!!!

    A tiny adjestment you can make:

    • For a smoother color change, add the line below to the <a> elements:
    a {
      transition: background-color .5s color .5s;
    }
    

    This ensures that the color will change after 500 milliseconds. Which makes it look better.

    Keep up the grind🫡

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 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