Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive Social Links Profile using HTML/CSS

Florian•120
@304fxn
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ehsan Tatasadi•1,800
    @tatasadi
    Posted over 1 year ago

    Hey there,

    Great job on completing this challenge! Your implementation demonstrates a good understanding of HTML and CSS, and the overall design looks visually appealing. Here are a few suggestions that could help further enhance your project:

    Semantic HTML Elements: Consider using more semantic HTML elements instead of relying solely on div and span tags. For instance, the name could be enclosed in an h1 or h2 tag, and the occupation description could use a p tag. Semantic elements improve accessibility and SEO, and they make your HTML more readable and meaningful.

    Use Anchor Tags for Links: For the social media links, it's semantically more appropriate to use <a> tags rather than span. This not only improves accessibility but also ensures that users and search engines recognize these as clickable links. Don't forget to include the href attribute pointing to the respective social media profiles.

    Body Background Color: To align your design more closely with the original design, consider setting the background color of the body to a dark shade. This will create a better contrast with your card and enhance the overall look and feel of your webpage.

    Responsive Width for Links: Instead of setting a width of 35vh for the links, consider making them width: 100% of their parent container. Then, set a max-width to the parent container (.container). This approach ensures that the links are responsive and maintain an appropriate size relative to their container, preventing them from becoming too wide on larger screens.

    Overall, you're on a great track! Implementing these suggestions will not only make your project more semantically correct and accessible but also enhance its responsiveness and alignment with design best practices. Keep up the excellent work and continue to explore and refine your skills in web development! 🚀

  • Renandx10•50
    @Renandx10
    Posted over 1 year ago

    put width: 100vw;height: 100vh; in the body with flex display, align item : center and justify content :center

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

Oops! 😬

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

Log in with GitHub