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

Profile card component using CSS Flexbox & Grid

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

Solution retrospective


I struggle at positioning the background pattern. Also, I'm not really sure about the sizing for each elements.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sarah•580
    @AutumnsCode
    Posted almost 2 years ago

    In your CSS I would add at every start of a project. :

    *, *::after, *::before {
    box-sizing: border-box;
    }
    

    The border-box tells tells the browser to account for any border and padding in the values you specify for an element's width and height. If you set an element's width to 100 pixels, that 100 pixels will include any border or padding you added, and the content box will shrink to absorb that extra width. It helps since you don't have to put a specific width on everything. I usually use one certain width on the outside container, and then use like width: 100% if needed. However, by the avatar, I would suggest to keep it the way you use it, maybe play with it to get it closer to the design.

    Some people add margin: 0 and padding:0 in there too, but it up to you.

    Here is some things I find rather helpful:

    • Reset the default styling by using one of the css reset out there e.g. Modern css reset by Andy Bell
    • Little help from one of the user here fedmentor

    If you have more question let me know.

    Marked as helpful
  • Dessidy•300
    @Dessidy
    Posted almost 2 years ago
    
    background-image: url(bg-pattern-top.svg), 
    url(bg-pattern-bottom.svg);
    
    background-repeat: no-repeat;
    
    background-position: right 52vw bottom 35vh, 
    left 48vw top 52vh;```
    
    This is for the back ground positioning in the body
    Hope this helps 😁
    

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