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

Social links profile

tailwind-css
P
jeffgrahamcodes•260
@jeffgrahamcodes
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 closely the final design aligns with the provided mockups. The layout is clean and visually appealing, with well-organized typography and spacing. Using CSS variables for colors, spacing, and typography made the code more maintainable and scalable. Additionally, implementing responsive designs for different screen sizes ensured the layout looks great on mobile and desktop devices.

Next time, I’d focus on improving accessibility by adding meaningful alt text to images and testing the solution with screen readers. For instance, the alt attribute for the profile picture could include a description, such as “Portrait of Jessica Randall.” I’d also explore making the buttons more interactive by incorporating hover states and animations for a better user experience.

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

The biggest challenge was ensuring the buttons were properly responsive across all viewports, particularly on smaller screens. Initially, the buttons’ widths didn’t align correctly, so I used width adjustments in media queries to make them adapt seamlessly to narrower viewports. Another challenge was maintaining consistent padding and spacing between elements, which I overcame by using a design system with CSS variables to centralize these values and make them reusable.

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

I’d like feedback on my approach to responsiveness, especially in ensuring consistent spacing and alignment across all devices. Additionally, I’m interested in learning if there are more efficient ways to handle button states (hover, focus, active) for improved accessibility and interactivity. Finally, I’d appreciate advice on further enhancing the project’s semantic structure and overall accessibility.

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 jeffgrahamcodes'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
  • Use cases

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