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

Social links profile using HTML and CSS

razanabbas•150
@razanabbas
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 proud of the progress I am making in my CSS skills, thanks to frontend mentor. I used a CSS reset and a CSS lint as the guy from Discord advised me last time and they turned out to be really helpful. I will start using them more in my upcoming projects.

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

I made some stupid mistakes which got me stuck for a while but I reviewed my code several times and discovered them.

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

Nothing specific this time, just any general feedback would be helpful!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan de Bruijn•3,220
    @DylandeBruijn
    Posted about 1 year ago

    Hiya @razanabbas,

    Congratulations on a good looking solution to this project! Happy to hear that you were able to make good use of a CSS reset and CSS lint. Everyone makes mistakes when working on a project, and Bob Ross would say they are happy little accidents. Being critical of your own work is a good skill to have! You made good use of semantic HTML elements and clear descriptive classes, props!

    A bit of friendly constructive feedback:

    • You could try adding a bit of padding to your body tag so the card has a bit of space between itself and the viewport.

    • If you want have a look at CSS variables / custom properties, they help out a great deal when you use the same value (colors for example) in your codebase, while giving them a descriptive name at the same time.

    • You could replace the h3 elements in your list by a tags because they are supposed to be linking to the relevant websites. Good job on the styling!

    Everything else looks great! I would appreciate it if you could mark my feedback as helpful when you have the chance and if it helped you out.

    Happy coding!

    Marked as helpful
  • Dan P.•270
    @Danielfww
    Posted about 1 year ago

    Hey razanabbas - great job on finishing this project! If I would recommend anything - it would be adding a href into your divs and doing hovers, that way your text would change when clicked on. Everything can be done in html so you dont have to chance your css file. Good luck and great job!

    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

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