Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

responsive Profile card component

syybiecoder•200
@syybiekarim
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


i know i did stuff wrong here can yall please tell me i also have some questions :

  • how can i have the background image ( the small blue one behind the profile pic ) skip the profile image border like the challenge has? i tried margin and padding but it didnt work
  • I STRUGELD a lot to get that background image to that place on top left but i never figured how to have 2 background images like the one in the challenges so i can put 1 in top left and the other one in the bottom right?
  • why is there a big vertical space between the profile image and h1 out of nowhere (i had to add negative 2rem to fix this weird problem)
  • why border radius on the main tag doesnt do anything even tho it contain all the card
  • i used hr tag for the line how can i make it lighter?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sean Gray•690
    @seangray-dev
    Posted over 2 years ago

    Hey there, nice job on this challenge. I got a couple suggestions that may help 😁.

    • To answer your first question you could try something like this on your profile pic:
    #profile-pic {
        border: 5px solid white;
    }
    
    • You can add multiple background images by separating them with a comma, and same with the positioning.
    body {
    background-image: url(...), url(...); 
    background-position: top left, bottom right; 
    }
    
    • By default heading elements come with a default margin property to them. I personally reset a lot of my CSS, which you can check this here to avoid this issue in the future: https://gist.github.com/Asjas/4b0736108d56197fce0ec9068145b421

    • Instead of using the hr tag you could use a border top or bottom to one of the other elements.

    section#second-section {
    border-top: 1px solid hsl(0, 0%, 59%);
    }
    

    Hope this helps! Keep it up and good luck 😁

    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