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

HTML5 for semantic structure , CSS3 for layout and styling

Kama•110
@Kama-ds10
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 proud of how I was able to personalize the project by adding my photo and customizing some of the colors to reflect my style. It made the challenge more meaningful and allowed me to apply basic HTML and CSS skills practically. I also kept my code clean and organized, which I’m intentionally working on.

Next time, I’d like to make the layout more responsive on smaller devices and experiment with adding some hover animations or transitions to the links for a smoother user experience. I also want to explore using semantic HTML more thoroughly and improve accessibility.

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

One of the main challenges I faced was centering the content both vertically and horizontally using CSS. It took some trial and error to get the layout to look the same across different screen sizes. I eventually solved this by using Flexbox and reviewing documentation and tutorials for proper alignment techniques.

Another small challenge was making sure my photo was sized correctly and displayed as a circle. I used border-radius: 50% and adjusted the dimensions to make sure it looked neat.

These issues helped me become more confident in debugging basic layout problems and deepened my understanding of Flexbox and image styling.

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

I’d appreciate feedback on the responsiveness of my layout—especially how it performs on smaller screen sizes. I’m also interested in learning how to improve the accessibility of my code (e.g., proper use of semantic HTML and alt text).

Additionally, if anyone notices ways I can clean up or optimize my CSS—such as better naming conventions or using more efficient selectors—I’d love to hear your thoughts.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kama's solution.

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.