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

Profile card component

Kaung Lun•110
@lunk-kml
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had some trouble dealing with the 2 background images that I suppose to put in this challenge. I try to make it a close as possible the best I can.

Also, it took me a couple of attempts to make text elements appear next to each other using wither inline or inline-block.

So far, I think I did everything I can to make my solution look close to the image on both versions of desktop and mobile.

Feel free to check out my code. I welcome any feedbacks, tips, and ideas. i have more to learn and improve.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • yishak abrham•2,150
    @yishak621
    Posted over 2 years ago

    The main challenge of these project is to practice the svg background adjustment ...so to make long story simple here is how u done these project...u are given two circular shaped svg picture and background color ...so the background of the card is the mixture of three things ....but unfortunately the circles are aligned center so first u will add them and push the bottom svg picture out of the screen by psuedo elments /*adding the top svg after the container*/ .container:after {   top: 100%;   left: 100%;   background: url('./images/bg-pattern-bottom.svg') no-repeat top left; /*to expand to top and left*/ } and for the top svg pic u will first place it in the center by /*adding the top svg before the container*/ .container:before {   top: 0;   left: 0;   background: url('/images/bg-pattern-top.svg') no-repeat bottom right; /*to expand to bottom and right*/ } and then for the whole container that is the parent of all /*Containers*/ .container {   display: flex;   min-height: 100vh;   flex-direction: column;   justify-content: center;   align-items: center;   position: relative;   overflow: hidden;   background: var(--color-one);   z-index: -1; } if u notice in the above i say position relative to place its circular svgs absolute..then here comes the magic part finally u will move both svgs to the left -50% and to the top -50% /*psuedo elments*/ .container:before, .container:after {   position: absolute;   content: '';   width: 100vw;   height: 100vh;   background-size: auto;   transform: translate(-50%, -50%); /*to the left and top*/   z-index: -1; } if u don't know about psudeoelments after and before please review again thanks

    Marked as helpful

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