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

profile card component with flexbox and CSS grid

James King•250
@jamesaking02
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I could not figure out how to get the background images positioned correctly. It was really frustrating, so I just omitted them. I would love some input on how to do it correctly, and then I can resubmit.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    BACKGROUND iMAGE 📸:

    • Looks like the background images has not been set yet, So let me share my css snippet which helps you to easily apply the background color with the background svg they provided to place perfectly as same as design.

    • Add the following style rule to your css, after completing these steps you can experience the changes.
    body {
      background: url(./images/bg-pattern-top.svg), url(./images/bg-pattern-bottom.svg);
      background-position: right 52vw bottom 35vh, left 48vw top 52vh;
      background-repeat: no-repeat, no-repeat;
      background-color: hsl(185deg, 75%, 39%);
    }
    

    • Tip: you don't want to resubmit new solution, instead just update your solution by commiting new changes to your github repository then just generate a new screenshot after editing the css file. That's all now your solution has been presented as new one

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • Caleb Bankole•230
    @BankoleCaleb
    Posted about 2 years ago

    For positioning the background images at the top left and bottom right, you'd use this style:

    background-position: 0% 0%;

    That's basically the format, I think you should be able to edit the value to suit your need. You could also use negative values. Note that you are putting the style on the body.

    background-position: left top;

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