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

Profile Card Component using Github

Efosa Collins EVBOWE•365
@efecollins
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


There are no questions now but I need a whole lot of feedback. Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elizabeth•460
    @gelizabeth
    Posted over 4 years ago

    Hi! If your question is about card background - create div with height and width you need and set background: url("path to your svg"). You can set it's border-radius so there will be no need to change your svg. Happy coding! :)

  • Helder Balbino•45
    @HelderBalbino
    Posted over 4 years ago

    Hello Collins

    Answering your questions, you can make an SVG as a background img using the normal css property: background-image: url(images/bg-pattern-bottom.svg),

    I've tried doing that using the imgs as background-image, but It was too hard for me to get the desired design, so I found that it's better to put the images on the html and use them inside a div with position: absolute , and the set a parent div with position: relative

    my solution to the problem;

    section .background { height: 100%; width: 100%; overflow: hidden; position: relative; }

    .background div:nth-of-type(1) { position: absolute; top: -425px; left: -350px; }

    .background div:nth-of-type(2) { position: absolute; bottom: -550px; right: -300px; }

    Hope my explanation helps you! feel free to ask for help anytime :)

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