Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Social links profile using HTML & CSS

P
mohammedAdelAv•60
@mohammedAdelAv
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Oscar Echenique D.•80
    @OscarE2D
    Posted about 1 month ago

    ✅ Positive Aspects

    1. Clear file structure: The project is organized with a css folder for styles and an index.html file in the root, which makes the code easy to navigate and understand.

    2. Use of pure HTML and CSS: Implementing the project without frameworks shows a solid understanding of web development fundamentals.

    3. Flexbox implementation: The use of Flexbox for layout indicates a modern and efficient approach to arranging elements.


    🛠️ Suggestions for Improvement

    1. HTML semantics:

      • Consider using semantic tags like <main>, <section>, or <nav> instead of <div> to improve accessibility and SEO.
    2. alt attributes in images:

      • Make sure all images have descriptive alt attributes to enhance accessibility for screen reader users.
    3. Responsiveness across devices:

      • Implement media queries to ensure the layout adapts properly to different screen sizes.
    4. Separation of styles:

      • It’s best to keep styles in external CSS files and avoid inline styles to improve code maintainability.
    5. Use of relative units:

      • Consider using relative units like rem or em instead of px to enhance the scalability and accessibility of the design.

    💡 Additional Recommendations

    • Code validation: Use tools like W3C Validator to check the validity of your HTML and CSS.

    • Image optimization: Make sure images are optimized for the web to improve loading times.

    • Naming consistency: Maintain consistent naming conventions for classes and files to facilitate code maintenance.

    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