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

CSS, FLEX and HTML

Yewande Adeyemi•110
@Wandesanguine
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have a problem in setting up the body background the way it should be. I find it very difficult to add the corresponding images and placing it where they shooud be. I will be very glad if sosmeone can help me out in doing this. Thank you guys. HAPPY CODING.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted almost 3 years ago

    Hi@Wandesanguine , for the svg background patterns i used them as background-image in the body like this :

    body {

    background-image: url(./images/bg-pattern-top.svg), url(./images/bg-pattern-bottom.svg);

    background-repeat: no-repeat, no-repeat;

    background-position: right 60vw bottom 39vh, left 60vw top 39vh; }

    You could check my solution for more details .

    I hope this help you .

    Marked as helpful
  • Veronica Orozco•260
    @VLOrozco
    Posted almost 3 years ago

    Hey Yewande,

    Mohammed had great things to say, especially with the svg files!

    As far as positioning them on your webpage, research position absolute/relative (but be careful as they can also create extra whitespace at the bottom of your screen if not used appropriately) - then use transform:rotate(__deg) to turn the image to match the design [insert the number before percentage mark for degree in the rotate value];

    Hope that helps! Happy coding to you too! ~V

    Marked as helpful
  • Account deletedPosted almost 3 years ago

    @Wandesanguine You forgot to add height: 100vh; & width: 100vw; to the body

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

Oops! 😬

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

Log in with GitHub