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

CSS HTML

Nima•30
@Nima155
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The circles are a pain! I have no idea how someone would go about centering them.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • John Rey Faciolan•220
    @juani2
    Posted about 4 years ago

    Hello Nima,

    Nice work on the card component. Regarding the circles, you mean the two circles on the upper and bottom corner?

    Well, in my case those two circles took most of my time positioning them for all screen sizes, they were a real challenge for me.

    I looked at your code and observed you implemented those two circles using <img> tag and position them using absolute units. Maybe you can try to position your images using viewport units so that when screen size change, your images will change position relative to viewport.

    you check this snippet from my own solution:

    .profile-card-section {
        background-color: hsl(185, 75%, 39%);
        background-image: url('/images/bg-pattern-top.svg'), url('/images/bg-pattern-bottom.svg');
        background-repeat: no-repeat, no-repeat;
        background-size: contain, contain;
        background-position: top -35vh left -35vh, bottom -35vh right -35vh;
        display: flex;
        align-items: center;
    }
    

    In my case I implemented those two circles CSS background, and position those images using background-position on CSS the offset values were taken from dozen trials resizing the screen for mobile tablet and desktop view port which is a real pain.

    for my complete solution, you may also look at this link:

    my solution

    Hope this one helps. Thanks.

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