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

Social Links Profile Solution

pchalaia•30
@pchalaia
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

It would be interesting to know how to make the padding-top and padding-bottom smaller for mobile devices without using media query. With clamp()? Has anyone tried this?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Asilcan Toper•2,960
    @KapteynUniverse
    Posted 8 months ago

    Clamp is one way like you suggested. You can also combine min and calc together.

    .card {
    .
    .
    .
        /* padding: 40px 28px; */
        padding-block: min(calc(100vw / 20), 40px);
        padding-inline: min(calc(100vw / 40), 20px);
    .
    .
    .
    }
    

    This means padding block (top-bottom) and inline (right-left) will be max 40px-20px but when 100vw/20-40 is smaller than 40px-20px, which is below 800px screen size, padding will be at that value. At 600px 30px-15px for example.

    I think you don't need to set role=main since you already used main landmark.

    Using max-width is nice, i also recommend you to use rem and a modern css reset or you can check Andy Bells reset too.

    Marked as helpful
  • jardellprod•100
    @jardellprod
    Posted 8 months ago

    I like how you modified the information provided to make it more personal. You also made the buttons hyperlinks I think that's actually pretty cool.

    I think you succeeded in completing the project !

    You also did a great job using max-width for the card size, this really made everything much more responsive. Also great use of the clamp function to size the text accordingly.

    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
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