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

Social Profile Links Card

Matthew Lancaster•120
@lank81
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I cleaned up some of the ways I was displaying text on the screen and broke my HTML down into a more semantic style.

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

Setting up a section and all divs within it receiving the styles. I needed to look this up and found a solution pretty quickly via Google.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Natali 👻 Grimm•1,190
    @Grimm-N
    Posted 9 months ago

    I really appreciate the work you’re doing! 🎉 Your coding skills are impressive, and I can see the effort you put into your projects. To make your code even better, here are a few suggestions:

    Improve Mobile Responsiveness 📱: I recommend enhancing the code to ensure the design is optimized for mobile devices. Because let's face it, no one wants to zoom in to read your amazing content! 😅

    Use Consistent Units 📏: Consider using units like rem, em, vh, vw, and % for layout and sizing throughout your code. These units are like the Swiss Army knife of responsive design—versatile and handy! 🛠️ I’ve noticed you're using them partially; expanding their use globally can make a big difference.

    Aim for Template-Like Code 📑: Try to structure your code to resemble established templates as closely as possible. This approach not only helps us learn but also enables us to tackle challenges like pros—just think of it as leveling up your coding skills! 🎮

    Get Familiar with BEM 🏷️: Start getting into the habit of writing classes using the BEM (Block Element Modifier) methodology. It’s like giving your code a neat and tidy haircut—so much easier to manage and understand! 💇‍♂️

    Keep up the great work! I’m excited to see how your projects evolve! 🚀

  • Babatunde Owolabi•80
    @nottundeednut
    Posted 9 months ago

    The font-weight of the links is not applied.

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