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

Social Links Profile using HTML, CSS

srinu-vinay-kumar•240
@srinu-vinay-kumar
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 am most proud of how I managed to create a responsive design that looks good on both mobile and desktop screens. Ensuring that the layout adjusted seamlessly to different screen sizes was a significant achievement for me. Next time, I would focus more on optimizing my code for better performance, including reducing the load time and improving accessibility features. Additionally, I would incorporate more user feedback early in the development process to refine the design and functionality.

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

One of the main challenges I encountered was dealing with cross-browser compatibility issues. Some features that worked perfectly in one browser did not behave the same in another. To overcome this, I used tools like BrowserStack to test my site across different browsers and devices. I also researched and implemented various polyfills and CSS hacks to ensure consistent behavior. Additionally, I had to deepen my understanding of CSS Flexbox and Grid to solve layout issues, which I managed through online tutorials and practice.

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

I would like help with improving the efficiency and cleanliness of my CSS code. While my design is functional, I feel there may be more effective ways to structure my styles to reduce redundancy and improve maintainability. Additionally, I'm seeking advice on enhancing the accessibility of my project. Ensuring that my HTML and CSS are optimized for screen readers and other assistive technologies is important to me, and I would appreciate guidance on best practices. Lastly, feedback on how to better organize my HTML structure for readability and future scalability would be very beneficial.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted about 1 year ago

    Hello there!

    Congrats on completing the challenge! ✅

    Your solution looks great!

    I have one suggestion:

    • When using the tag <img>, make sure to set the correct path, otherwise your code won't be able to find the image. And if your code can't find it, it won't show.

    📌 This is your code:

    <img src="/avatar-jessica.jpeg" alt="avatar">
    

    📌 And here's the update with the correct path:

    <img src="./avatar-jessica.jpeg" alt="avatar">
    

    The difference is just a dot but it's enough to prevent your image from showing.

    I hope it helps!

    Other than that, great job!

  • Justin Levy•100
    @justinsane
    Posted about 1 year ago

    Nice work!

    Did you use generative AI for the 'solution retrospective'? I'm confused why you mentioned optimizing code and cross-browser compatibility issues for such a simple web component.

    A few areas to explore:

    • can you create hyperlinks to the social media sites?
    • should the buttons be wider?
  • khannfouad•230
    @khannfouad
    Posted about 1 year ago

    Semantic tags make HTML much more readable whereas Using CSS's in-built properties like inheritance and cascade plus grouping selectors ensures that your CSS is readable and clean. Happy Coding 🌺

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

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

Oops! 😬

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

Log in with GitHub