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

Responsive links profile using clamp and min dimensions

P
rmmcfarlin•240
@rmmcfarlin
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 didn't have access to the Figma file, so I'm happy that I got it close by eyeballing it. It would have been nice to have access to the design file to get everything more dialed in.

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

Getting it to be responsive and keep its form while shrinking down to smaller sizes for mobile. I used min and clamp to get it to work on 375px viewports, but I couldn't get all of the elements (Mainly the links / buttons) to stay the correct size ratio down to 325. This is something I will work on moving forward.

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

Any general advice / tips on responsiveness.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nicolette Reneilwe Mashaba•140
    @Reney17
    Posted 6 months ago
    1. Cross-Browser Compatibility Issues:

    Still facing layout inconsistencies across certain browsers. Seeking best practices for handling these issues, particularly with CSS Grid/Flexbox. 2. Optimizing Mobile Responsiveness:

    The website is responsive, but you want to improve fluidity on various screen sizes, especially in navigation and footer sections. 3. Git and Version Control Best Practices:

    Encountered issues with pushing changes due to broken references. Looking for advice on managing large repositories and avoiding similar issues in the future. 4. Code Documentation:

    Unsure about the best way to document the code for better clarity. Seeking advice on best practices for writing clear, concise documentation for your project.

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