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

Social links profile using Flexbox

foo-lin-xuan•30
@foo-lin-xuan
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 am learning frontend development and aiming to work as one eventually. I would greatly appreciate any tips and feedback!

I worked on improving my approach based on feedback on my previous challenge, and guidelines from reading online. This time round, I approached the challenge by:

  1. Using CSS reset
  2. Taking care to write semantic HTML
  3. Using BEM naming convention
  4. Naming components for better selector intent
  5. Taking mobile-first approach
  6. Using rem for media queries

I have not styled focus states before this and I nearly missed that out. Next time, I will take note of this for keyboard interactions.

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

I faced challenges when trying to style the links to look like buttons, as the box sizes were hugging the text. What I had to do, since they are contained inside a flex container with flex-direction: column, was simply to add the property align-self: stretch to the links.

Another challenge I encountered was that there are no bottom/right padding when the card height/width is greater than viewport height/width. I was not able to resolve this.

What specific areas of your project would you like help with?
  1. Why does body not have bottom padding when the viewport height is smaller than the card height? Similarly for right padding with viewport width and card width.

  2. In the Figma file, the transition/interaction has 'Animation' (set to Dissolve) and 'Curve' (set to Slow) settings. Are there any resource/references on how to translate these to CSS?

  3. I would love to receive feedback on any good practices to have, and improvements that I can make.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on foo-lin-xuan's solution.

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

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.