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

Responsive social profile card using Flexbox

accessibility, bem, pure-css
Michael Okorie•150
@Michael-Okorie
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 proud of how polished and responsive the final result turned out. The design remains consistent across different devices, and the interactive states feel smooth and intuitive. Next time, I would experiment with adding subtle animations and transitions to enhance user engagement and explore organizing styles using a preprocessor like SCSS for better scalability.

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

Getting the layout to remain centered and well-balanced across screen sizes was a bit tricky. I had to fine-tune padding, margins, and max-widths to ensure visual harmony. I also spent time ensuring that the hover and focus states were accessible and visually distinct. Frequent browser testing and using dev tools helped me iron out these issues.

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

I'd appreciate feedback on:

  • How I structured the layout and responsiveness

  • My use of CSS custom properties and Flexbox

  • Whether there's a more scalable approach to organizing styles in a small component-based layout

  • Any accessibility improvements I might have missed

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elmar Chavez•500
    @CodingWithJiro
    Posted 23 days ago

    First, your site is fantastic for devices with screen width 320px and up.

    What I would like to suggest is for your CSS custom variables to be all in uppercase so its easy for other developers when they are inspecting your code.

    Keep on practicing, keep on coding!

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