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

Social Links Profile (HTML | CSS)

Cheosphere•1,040
@Cheosphere
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


...made with a lot of love 🤘🏻🙂

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Md Mazhar Ali•440
    @Mazhar1857
    Posted about 1 year ago

    I'm facing an issue with the social-link-profile webpage, which I've noticed is also occurring on your page. When inspecting the live URL and setting responsive dimensions for mobile, such as choosing iPhone 12 Pro and rotating it into landscape mode, there are problems that occur when scrolling down, i have added some border for more visibility in my project. i will be very thank full if you help me out. i am using google chorme.

    Marked as helpful
  • Nantue Polchevski•170
    @Nantue
    Posted over 1 year ago

    How do you know the perfect pixel of the cards?

  • Justin Connell•720
    @justinconnell
    Posted over 1 year ago

    Pixel perfect!

    I noticed that you use straight up CSS and that your code is well structured and readable - I also noticed that you use class selectors and element selectors in the CSS codebase - if you were working on a larger project would you use class selectors instead of element selectors?

    The reason I ask is because I've been reducing the amount of base HTML I touch and opting for a more BEM type of approach to class names - my thought is that this eliminates problems with 'specificity' but has the downside of increasing the size of the CSS codebase.

    I'm very interested in your take on this - thanks so much for your time.

  • Augustine Edeh•110
    @Augustine-edeh
    Posted about 1 year ago

    Nice work man!

  • Heba Ahmad Saleh•250
    @hebaahmedsaleh
    Posted about 1 year ago

    it is pixel perfect, amaaazing but I have a question you are working with px for example the links has fixed height 45px ? but in real life work designers always request getting dynamic heights according to internal paddings and font-size. I think if we know the screen size of the implemented. it can be calculated not to be static height, what do you think ?

  • SierLor•400
    @SierLor
    Posted over 1 year ago

    Es realmente perfecto. Enhorabuena por el resultado¡¡

  • shalomkerry•260
    @shalomkerry
    Posted over 1 year ago

    its so perfect. Well done mate.

  • Matthew Kuria•170
    @matthewkuria
    Posted over 1 year ago

    Great implementation!

  • Dashaun Sutton-Harris•80
    @dashaunn
    Posted over 1 year ago

    You're my inspiration 🤩 Beautiful work as usual @Cheosphere 👍🏾

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

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

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

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

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