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

Social Links Profile using HTML & CSS Flex

Dias•140
@adambeckercodes
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? What I’m Most Proud Of

I’m most proud of the overall design and accessibility of my project. The use of CSS variables for consistent spacing, colors, and font sizes made the styling process more manageable and reusable. I also ensured that the project is responsive and accessible, with features like ARIA labels, focus-visible styles, and hover effects.

Another highlight is the modern and polished look of the card component, with smooth transitions and a visually pleasing box shadow effect that enhances its appeal. I’m also happy with how the links adapt to hover and focus states, ensuring both usability and interactivity.


What I Would Do Differently Next Time

Next time, I would focus more on:

  1. Improving Responsiveness: The project is currently optimized for small screens and tablets, but I’d like to add more breakpoints for larger screens to ensure it scales seamlessly across all devices.
  2. Animations: Adding subtle animations for hover and focus interactions could enhance the user experience further.
  3. Content Dynamism: Incorporating JavaScript to dynamically update or fetch content for the card would make the project more functional and versatile.
  4. Testing Accessibility: While I’ve added ARIA labels and focus styles, testing with screen readers and other assistive technologies would ensure better accessibility for all users.
What challenges did you encounter, and how did you overcome them? Challenges I Encountered

1️⃣ Positioning and Responsiveness

One of the biggest challenges I faced was ensuring the layout remained responsive across various screen sizes. It was tricky to adjust the spacing, alignments, and scaling while keeping the design consistent.

2️⃣ Hover and Focus Interactions

Creating hover and focus effects for the links while ensuring the entire parent element (``) responded correctly took some trial and error. Using pseudo-elements effectively without breaking the structure was particularly challenging.

3️⃣ Accessibility

Ensuring the project met accessibility standards, like adding appropriate ARIA labels and focus-visible styles, required additional research and testing to get it right.


How I Overcame Them

Positioning and Responsiveness

To address the responsiveness issue, I implemented a mobile-first approach with well-defined breakpoints using media queries. I tested the design on different device sizes and adjusted the layout dynamically for each screen width.

Hover and Focus Interactions

I solved the hover and focus challenge by using ::before pseudo-elements on the tags and ensuring their dimensions matched the parent elements. Setting the `` to position: relative and extending the clickable area with the pseudo-element made the interactions seamless.

Accessibility

I referred to MDN Web Docs and accessibility guidelines to understand how to use ARIA attributes effectively. Testing the project with keyboard navigation also helped me refine the focus-visible styles for better usability.

What specific areas of your project would you like help with? What Specific Areas of My Project Would I Like Help With?

1️⃣ Hover and Focus Effects
I’m happy with the current hover and focus effects, but I’d love ideas for making them more dynamic or visually engaging. Are there any subtle animations or transitions I could add without overwhelming the user experience?

2️⃣ Accessibility Enhancements
Although I’ve added ARIA labels and focus-visible styles, I’m always open to feedback on improving accessibility. Are there any best practices or tools I should use to ensure my project is fully accessible?

3️⃣ Content Dynamism
I’m considering adding JavaScript to make the card content dynamic (e.g., fetching data or updating content on the fly). I’d appreciate guidance on the best approach to implement this while keeping the project scalable.

Your feedback on any of these areas would be incredibly valuable. Thank you in advance! 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • webthingz•70
    @webthingz
    Posted 7 months ago

    Wow very nice Job! Inspiration for my next challenge! I would like to know how the size is prefectly matching the example. i could not find the size of the box in the assigment.

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