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

Profile Page Solution

vknir•130
@vknir
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 used CSS variables for the first time that I had learned while going through someone else's solution .

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

A recurring challenge in making a Front End Mentor challenges is to get margins, gaps, padding exactly as per the images provided. To overcome this, I use my estimation to get as close to images provided to us.

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

Some areas that I would like to helped on is get use/discover various CSS attributes. In this challenge, we had to change the cursor on hover, with the help of goggling I was able find how to target the cursor. If someone can tell me how to learn about other attributes in a fun way I will be eternally grateful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    MikDra1•7,470
    @MikDra1
    Posted 11 months ago

    If you want to make your card responsive with ease you can use this technique:

    .card {
    width: 90%;
    max-width: 37.5rem;
    }
    

    On the smaller screens card will be 90% of the parent (here body), but as soon as the card will be 37.5rem (600px) it will lock with this size.

    Also to put the card in the center I advise you to use this code snippet:

    .container {
    display: grid;
    place-items: center;
    }
    

    Hope you found this comment helpful 💗💗💗

    Good job and keep going 😁😊😉

    Marked as helpful
  • Hale•330
    @halelite
    Posted about 1 year ago

    hi @vknir!

    Good job! Your solution looks great!

    I just noticed a small thing about your CSS. In the design, the component is centered both horizontally and vertically. I suggest you center your component vertically as well, so your project looks way much better. There are a lot of ways to center it. Some of them are:

    • using flexbox

    • using margin or padding

    • using absolute position property

    position: absolute
    top: 50%;
    transform: translateY(-50%);
    

    Other that that great job! 👍

    I hope it helps!

    Marked as helpful
  • P
    Boris•4,130
    @makogeboris
    Posted about 1 year ago

    Hi vknir nice work, you can learn about different css attributes and on the MDN Web Docs website and also as you build different projects you'll come across different CSS properties.

    Here are some suggestions for improvement on your solution

    • All content should be wrapped within landmarks. Wrap a main tag around the .container
    • To improve the semantic meaning of these social media links, you should use the a (anchor) tag instead of the button tag. The a tag is used for navigation to other pages, while the button tag is designed for interactive actions like submitting forms or for events like toggling content. Also, using an unordered list ul to group the social media links is a better approach for both semantics and accessibility.
    • Avoid setting fixed heights and widths on elements, as this can create problems with responsiveness and content fit. Instead, let the content and padding determine the element’s size. If necessary, use max-width or min-height, and prefer relative units like rem for better adaptability. Change the width of the .container to max-width and it should be defined in rem.
    • Font-size should be written in rem not px. This article explains it better Why font-size must NEVER be in pixels.
    • Consider using a modern CSS reset at the start of the styles in every project. Like this one Modern CSS Reset.

    Hope this helps

    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

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