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

Responsive Social Links Profile with Custom Fonts & Flexbox

accessibility, pure-css
P
MAGENE Sem Joel•320
@Jomagene
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'm most proud of integrating custom fonts using @font-face and maintaining a responsive layout through a mobile-first approach. Next time, I’d explore CSS Grid for more complex layouts and focus more on performance optimization, like using font-display: swap and serving fonts in WOFF2 format for faster load times.

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

A significant challenge was creating a responsive design that adapts seamlessly across different screen sizes without overusing media querries. I used Flexbox for layout management, which allowed me to center elements both horizontally and vertically with the my custom classes .flex and .flex-center. Additionally, I employed a media query to adjust the width of the list of links on larger screens, ensuring a consistent and balanced layout.

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

Any suggestions for enhancing the code organisation and accessibility, would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Rupali•890
    @rupali317
    Posted 11 months ago

    Hello @Jomagene

    Great work on this challenge. I have the following feedback:

    • In terms of accessibility, you should never use pixels for font size because if I rely on large fonts and I go to my browser settings to alter the fonts to larger ones and then I come to your project, I will see that your fonts have not scaled. It is not great for accessibility. That has happened because you use pixels. Pixels are not good for scaling. Pixels are fixed. You should use rem instead.

    • For the quotes, you can use the <q> tag

    • I noticed that the right side of the image seems to be chopped off. Unfortunately, I am unable to upload the screenshot. This can be fixed by eliminating the <section class="image-container"></section>. It is not needed. Just the <img> related code is enough and in your CSS of the img, you apply the border-radius. You already have the height property for image. Try to keep the code simple. No need to complicate the code.

    • Another piece of advice: Your project should have a CSS reset otherwise different browsers will apply their own default stylings. We want a consistent look and feel in all the browsers. Refer to this CSS reset article

    Let me know if the above suggestions help

    Marked as helpful
  • tylerhyndman484•100
    @tylerhyndman484
    Posted 11 months ago

    Looks very close to the design! Very well done! I did notice though that the font for the name of Jessica Randall looks a little different than the one in the design; but very nice work!

    Marked as helpful
  • P
    MAGENE Sem Joel•320
    @Jomagene
    Posted 11 months ago

    @Rupali Thanks so much for the feedback! Was it helpful? Absolutely!

    You're right about the pixel font sizes. I'll be switching to rem for better scalability and accessibility—I finally understand why it’s so important, thanks to you. Great tip on the <q> tag for quotes; I'll start using that to keep things more semantic. Thanks for spotting the issue with the image being chopped off. I’ll clean that up. And the CSS reset? Yet another great lesson learned! The article you shared is fantastic, and I’ll be implementing a reset to ensure consistency across browsers.

    What a comment! I’ll be applying these updates right away. Thanks again!

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

Oops! 😬

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

Log in with GitHub