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

Profile Card Component using HTML and CSS

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

Solution retrospective


This is my second completed Frontend Mentor challenge. I struggled a bit with the positioning/alignment of the three stats components at the bottom. For now I've used a combination of flexbox and relative positioning to get the alignment, but I'm not totally happy with it. Is there a smoother way of solving this? My second issue is the two background images (the circles). Their positioning looks okay on a fullscreen desktop view, but they move when the window size changes, and it doesn't look right on mobile. How can I keep the position of these two images fixed relative to the card instead of relative to the body (I'm sure there is a very simple solution to this)?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hello Lmflolo, congratulations for your second solution!

    Here's my tips for you about the background circles:

    First of all remove the images from the html or use display: none to make them invisible:

    .bg-top, .bg-bottom {
        display: none;
    }
    

    An alternative add these two circles as a background, adding it to the body with two keys properties, background-image and background-position, note that the comma inside each properties declare the single modification for each circle separated.

    body {
        background-color: hsl(185deg, 75%, 39%);
        background-image: url(./images/bg-pattern-top.svg), url(./images/bg-pattern-bottom.svg);
        background-repeat: no-repeat, no-repeat;
        background-position: top -416px left -311px, bottom -633px right -149px;
        align-items: center;
        background-color: hsl(185, 75%, 39%);
    }
    

    👋 I hope this helps you and happy coding!

    Marked as helpful
  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello Lmflolo congrats on finishing the challenge! maybe I can help you with your question.

    I think you should set 3 different div blocks, one for followers, other for likes and other for the photos. Put them all in a container an align them as flex row.

    Then align each block as a column.

    Hope my feedback helps you, if you need any help or code examples about what I mean, don't hesitate to ask.

    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

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