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

SOCIAL LINKS PROFILE

echo-script0•180
@echo-script0
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 I created a clean, fully centered, and responsive social profile card with a sleek dark theme. I managed to handle the layout and styling just right so it looks great on different screen sizes — all with pure HTML and CSS, no frameworks. Also, I polished the hover effects on the social links to give a nice interactive feel!

Next time, I’d focus more on accessibility — making sure the colors have enough contrast and adding proper ARIA labels for screen readers. I’d also like to experiment with CSS animations or transitions to enhance the user experience even more.

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

One of the main challenges I faced was resizing the container and all its content so that the profile card wouldn’t overflow or fill the entire page. Initially, the container was too big and caused unwanted scrolling, which broke the fixed layout I wanted.

To fix this, I had to carefully adjust the container’s width and height, and scale down the font sizes and padding inside it to make sure everything fit neatly in the center of the viewport. I also used CSS Flexbox properties like justify-content and align-items on the body to perfectly center the container both vertically and horizontally.

Finally, I set overflow: hidden on the body to completely remove scrolling, so the page feels like a fixed, clean single card. This process taught me a lot about balancing responsive sizing with fixed layouts.

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

I’d love feedback on the overall design and responsiveness — especially how well the profile card scales on different screen sizes. Also, if there are any suggestions for improving the CSS structure or making the code more efficient, that would be super helpful. Finally, I’m open to tips on accessibility and best practices to make the project even better!

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 echo-script0'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.