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

Social Links Profile Page

sass/scss
dolapobj•310
@dolapobj
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 using proper BEM formatting when styling my SCSS styling. I think this helps keep my CSS readable for another user.

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

One of the main challenges was learning how to properly do the margins and use the box model correctly. I was able to overcome them by understanding the difference between content, padding, border, and margin correctly.

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

Because the nature of this design is rather narrow it already works well on smaller phone screens. I would like feedback on the responsiveness of the design. Do we always need to use media queries? Or for a design like this is it okay to design it such that it works on the smallest screens first, and then progressively gets bigger?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markobrien7•60
    @markobrien7
    Posted 5 months ago

    The solution looks really good to me. It was my first project using SAAS so it was good to see you are using it too. The only thing I can think of is design rules say most pages should have an h1 then the next h tag should be h2 then h3 etc. You shouldn't jump from an h3 to an h6. I think this is beneficial to screen readers.

    In regards to your question about responsiveness, the design for this between the different screen sizes is only a slight adjustment to the width so I think its ok not to have media queries for this particular challenge. I think it would be different if on the larger screens the buttons were horizontal and then they changed to vertical at a smaller screen size.

    Well done. Keep up the good work!

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