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

Social links profile. HTML | CSS | MOBILE-FIRST WORKFLOW

Hendrixx•430
@BeeAlmighty
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?
  • Honestly, i am grateful for the fact that i implemented my corrections on this project like BEM and semantic HTML.
What challenges did you encounter, and how did you overcome them?
  • I found it quite challenging implementing the mobile-first design and making sure my project was responsive across all screen sizes starting from the mobile phone.
  • Thanks to freecode camp and their elaborate content, i was able to successfully understand and implement them.
What specific areas of your project would you like help with?
  • I got introduced to the BEM concept from a detailed feedback from a user on my last project. In terms of implementation, it was the best so i'd need more eyes on my BEM code and feedbacks would be appreciated.
  • Also i need feedback on my code generally on ways, it could be cleaner and more concise.
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Thomas Weitzel•170
    @thomasweitzel
    Posted 7 months ago

    Your solution for the "Social Links Profile" challenge demonstrates good use of semantic HTML and a well-structured CSS approach. The layout is straightforward, responsive, and visually cohesive, aligning with the requirements of the challenge. There exists only minimal improvement in terms of accessibility, maintainability, and visuals.

    • The use of semantic elements such as <main>, <section>, and headings (<h1>) is excellent.

    • The media query ensures a responsive design for screens smaller than 425px.

    • Adjustments for font sizes and padding are thoughtful.

    • The hover effect on the .socials buttons is intuitive and visually distinct. The use of transition effects (transition: all 0.2s ease-in-out;) is a nice touch!

    • The CSS is well-organized and avoids unnecessary properties.

    • The inclusion of font-optical-sizing: auto; is an advanced CSS feature. Nice!

    • Missing alt attribute content: The alt attribute for the avatar image is empty. To improve accessibility, provide descriptive text such as alt="Jessica Randall's profile picture".

    • The attribution link (Your Name Here) should be updated to your name or GitHub profile. Be proud of your work!

    • You have tagged your solution to this challenge with the #react tag, although it's not a React application.

    Your solution effectively meets the challenge requirements with only minor room for improvement in accessibility. Great job!

    Marked as helpful
  • Adriano•42,870
    @AdrianoEscarabote
    Posted 7 months ago

    Hey Hendrixx, how’s it going? I was really impressed with your project’s result, though I have some advice that could be helpful:

    To improve the semantics and accessibility of your code, consider using the <ul> (unordered list) element to group related links. The <ul> tag is ideal for representing collections, such as a list of social media links or navigation items.

    Using <ul> not only makes your code more structured and meaningful, but it also helps assistive technologies identify the group as a related set of items, enhancing the experience for screen reader users. Additionally, this approach improves overall readability and maintainability of your HTML.

    Example:

    <ul>
      <li><a href="#">GitHub</a></li>
      <li><a href="#">Frontend Mentor</a></li>
      <li><a href="#">LinkedIn</a></li>
      <li><a href="#">Twitter</a></li>
      <li><a href="#">Instagram</a></li>
    </ul>
    

    In this example:

    • The <ul> wraps the entire group, indicating that these links are related.
    • Each item is enclosed in a <li> (list item), which provides a clear structure and logical grouping.

    This method is particularly useful for navigation menus, social media links, or any set of grouped items, offering better support for both SEO and screen readers.

    Pro Tip: Avoid using <div> elements alone for lists, as they don’t convey the same semantic meaning. Whenever possible, choose semantic tags like <ul> or <ol> to improve the quality of your code.

    Everything else looks great.

    Hope this helps! 👍

    Marked as helpful

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

Oops! 😬

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

Log in with GitHub