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

Profile Card Component

Abd-ur-Rahman•45
@Abd-ur-Rahman03829
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 completed the challange but i have a samll problem that how can i change the position of background bubbles.... Any suggestion about that would be very helpfull.... Thanks in advance.....

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shahin NJ•1,190
    @SJ-Nosrat
    Posted about 4 years ago

    Hi Rahman, since you've added the bg-pattern-top and bg-pattern-bottom as background-images you should use the background-position property to postion them. Here you can find the MDN article on background position.

    Be sure to add background-repeat: no-repeat as CSS by default repeats the image in a tiles starting from left to right and top to bottom.

    Also, with regards to the REPORT is due to HTML accessibilty issues; in other words you should try and use semantic HTML that way you convey meaning to your HTML structure.

    Instead of a <div> for your .card class, you can use: an <article> element. Here is a good article by W3 Schools.

    Hope that helps!

    Best of luck with your coding journey!

  • Anmol Kapil•655
    @anmolkapil
    Posted about 4 years ago

    Use "position:absolute" property on bubble svg. Then adjust their position accordingly.

  • Moeen Mahmud•180
    @moeen-mahmud
    Posted about 4 years ago

    Hello Abd-ur,

    Your approach to the solution is good. For the background, you can use the images as "fixed position", something like below:

    .background_image--top {
      position: fixed;
      bottom: 45%;
      right: 50%;
    }
    
    .background_image--bottom {
      position: fixed;
      top: 50%;
      left: 45%;
    }
    

    You can view my code here: https://github.com/moeen-mahmud/profile-card-component

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

Oops! 😬

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

Log in with GitHub