Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Social Links Page Solution Using HTML and CSS Flex Box

Ashim Raj•50
@Ashim-Raj12
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 how clean and structured my layout turned out. I was able to use semantic HTML and modern CSS to create a centered card layout with custom fonts, consistent spacing, and a responsive feel. I also enjoyed applying @font-face with multiple font weights and learning how to create smooth button hover transitions with effects like elevation and color change.

If I did this project again, I’d focus more on accessibility and making the links keyboard-friendly. I'd also explore making the layout more responsive across devices and adding dark/light mode support for a more polished experience.

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

One challenge I faced was making sure the card layout stayed clean and centered on all screen sizes without stretching too much on larger screens. I solved this by setting a max-width on the card and using Flexbox to center it both vertically and horizontally.

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

I’d appreciate feedback on a few key areas:

Responsiveness: I designed the layout for desktop, but I’d like to learn how to better adapt it for mobile and smaller screens using media queries.

Button styling: I added a hover effect with movement and box-shadow. I’d love suggestions on improving the animation or making it feel more polished or modern.

Accessibility: I’m unsure if my current structure is accessible for screen readers and keyboard users — especially around the buttons and text.

Code structure: I’d like feedback on whether my CSS is well-organized and if there are ways to simplify or make it more reusable.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ashim Raj'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.