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

Social links profile using HTML & CSS

P
Kyle Mulqueen•400
@kmulqueen
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'm most proud of creating a clean, accessible solution that maintains proper semantic HTML structure while achieving the desired visual design. Using appropriate HTML elements like unordered lists for the social links while styling away the bullet points helped me keep the code both semantically meaningful and visually appealing.

For future projects, I would:

  • Start with a more detailed plan for my CSS organization
  • Implement a more structured naming convention like BEM from the beginning
  • Take more time to document my code as I go, rather than after completion
What challenges did you encounter, and how did you overcome them?
  1. Styling links without losing accessibility: Initially, I struggled with removing the default styling of anchor tags while ensuring they remained accessible. I overcame this by researching best practices for accessible link styling, which led me to maintain proper focus states and hover effects.

  2. Creating consistent spacing across devices: Getting the spacing to look consistent on both mobile and desktop views required more adjustments than I initially expected. I solved this by adopting a more systematic approach to spacing with consistent CSS custom properties for margin and padding values.

  3. Maintaining semantic structure: I wanted to use a list for the social links, but didn't want the bullet points. Learning how to properly remove list styling while preserving the semantic structure helped me overcome this issue.

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

I would appreciate feedback on:

  1. Accessibility: Are there any ways I could improve the accessibility of my social links? Is my current approach with unstyled but semantic lists and links following best practices?

  2. Responsive design: Does my solution maintain proper proportions across different screen sizes? Are there any breakpoints I should add or adjust?

  3. CSS organization: I tried to keep my CSS organized, but I wonder if there are better ways to structure it. Would a methodology like BEM have been beneficial for this project?

  4. Performance optimization: Are there any unnecessary CSS rules that could be removed or combined to improve loading performance?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • FrontEndExplorer-Temp•70
    @FrontEndExplorer-Temp
    Posted 3 months ago

    Your commitment to learning and improving shines through in this project. The attention to detail and effort you've put into responsive design and accessibility are truly commendable—great job!

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