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

Social Links Profile using HTML, CSS/SASS

sass/scss
ChristianM•130
@DevXtianM
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've developed the whole project with minimal searching for tutorial :D

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    webdevbynight•530
    @webdevbynight
    Posted about 1 year ago

    Some feedback:

    • the design file shows that the links texts are permanently bold, not only when hovered;
    • you should enhance the semantics of your HTML: the attribution footer should be wraped by the footer element, the main content should be within the main element and the card should be tagged as an article or section element (don’t hesitate over having a look at the HTML elements reference on MDN);
    • you should use relative units for font sizes such as em or rem: when using pixels to set font sizes, I am afraid this can lead to accessibility issues with users needing to be able to zoom texts in (by the way, you can define all dimensions, widths, paddings, margins, gaps… by using relative units: the design will get more elastic);
    • when possible, avoid using fixed heights: if you need to set a height, to use min-height is preferable;
    • if you want the whole container to occupy the whole height of the viewport, think of min-height: 100 dvh (check for relative length units based on viewport if you do not know what such a unit stands for);
    • even if Sass is a great tool, you do not need to use Sass variables any more to define colour values, since CSS has custom properties;
    • on main.scss, line 41, just declare font-weight: bold if you want to use the bold weight of the font (since there is only one font used, declared previously, you do not need to use font-family again).

    I hope this feedback helps you.

    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