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

Social Links Profile Page

abdelrhman-mahmoud-awad•30
@abdelrhman-mahmoud-awad
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?

Pride: The most proud aspect might be the clean, responsive design that effectively presents social profile links. Improvements: In the future, you might consider adding more interactive features or enhancing accessibility.

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

Challenges: Implementing responsive design and ensuring cross-browser compatibility. Solutions: Using CSS Flexbox/Grid for layout and testing on multiple devices and browsers.

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

Responsive Design: Ensure the layout adjusts smoothly across various devices and screen sizes. Performance Optimization: Improve loading times and overall efficiency of the site. Accessibility: Check if the site is usable for people with disabilities, including keyboard navigation and screen reader compatibility. User Interface (UI) and User Experience (UX): Evaluate the design for ease of use and intuitive navigation. Cross-Browser Compatibility: Verify that the site performs consistently across different web browsers

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Supa-Thobile2•100
    @Supa-Thobile2
    Posted 11 months ago

    The project is excellent but not centred as in the design.

    The Desktop design has a scroll bar that will disappear when the container is properly centred.

    The code is readable and easy to follow.

    I love how the developer designed the social links that is a great design.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub