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

social-links-profile-main

pure-css
Awaisxd•40
@Awaisxd
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?

User-centric design: Received positive feedback on accessibility (e.g., keyboard navigation, contrast ratios).

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

CSS layout breaking on mobile->Used Flexbox + Grid rigorously, tested with Chrome DevTools->Mobile-first design saves time.

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

Make your layout mobile-friendly. Use media queries to adjust for tablets, desktops, etc. Optimize image scaling and font sizes for smaller screens.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    M Kerr•2,130
    @mkerr-github
    Posted about 2 months ago

    Here's a very good primer on responsive web design by w3 schools that I found useful. It's a great reference site for HTML and CSS, and a quick practice of the concepts.

    https://www.w3schools.com/html/html_responsive.asp

    Basically, you can use media queries, where you can specify in the CSS that certain properties and sizes should change once the pixel size of the screen reaches a certain size. Watch a few short tutorials on CSS and media queries.

    Here is a nice short explanation as well on W3 schools:

    https://www.w3schools.com/css/css_rwd_mediaqueries.asp

    For responsive purposes the convention is to convert pixel measurements to "rem". To do so divide the pixel value by 16 (as the base rem is 16px, because 16px is the default font size setting size on most browsers).

    Then use max-width to set the large widths for desktop and min-width to set the small widths for mobile. Try to let the browser set the heights of elements unless you need a very specific height.

    The convention is to use rem and sometimes em, instead of pixels for most items, as rem and em are more responsive than pixels. Pixels can be used for small elements like icons and buttons where you do not want the size to change even on small screens.

    More details here: https://austingil.com/px-or-rem-in-css/#:~:text=Pixels%20are%20an%20absolute%20unit,the%20equivalent%20of%2024%20pixels.

    If you found anything in this comment helpful:

    Please remember to click the ‘Mark as helpful’ button, thank you!

    Keep up the good work, and keep going! 👋

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub