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

Profile Card Component Built with CSS Flexbox, Grid & Css Positioning.

accessibility, bem
Johnny•490
@johnnysedh3lllo
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


hey guys, finally got another one done.

here are some of my observations from taking on this challenge.

#Difficulties-and-Uncertainties

  • although my major difficulty was being able to place the profile image at the specified position, i was able to get it done but i still am not exactly sure i took the best approach. please if you have suggestions in regards to a better approach, i would love to know about it.
  • secondly, i had a bit of an issue positioning the svg background image properly. i still got it done to some degree but I'm not exactly sure of it in terms of scalability on other viewports. if you do have an idea on the best way to position them, i am open to learn from you.
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 Johny, congratulations for your solution!

    You've done a really good work here, you've also used a shorthand for the background and this is amazing!

    I don't recommend you do it in this case, because the background will be a huge line of code to manage, try to use instead the properties separately.

    I've positioned the circles and you see the code below (note that you've to give some fine adjustments, but is working now)

    body {
        font-family: var(--ff-primary);
        background-color: var(--clr-primary-100);
        background-image: url(bg-pattern-top.svg) , url(bg-pattern-bottom.svg);
        background-size: cover;
        background-position: top -1086px left -618px, bottom -1146px right -370px;
        background-repeat: no-repeat;
        display: flex;
        justify-content: center;
        align-items: center;
    }
    

    Hope it helps and happy coding bro!

    Marked as helpful
  • Yeabsira•480
    @itsyaba
    Posted almost 3 years ago

    Hey Johnny , Nice Work

    Your code is really readable and that's nice and you could have used flexbox instead of position don't get me wrong both of them works but when you are coding a larger project using flexbox is more recommended because when you center items using position you could end up covering items that you don't want to cover up and it really pain in the ass to make it responsive after using position .

    Nice Work Keep It Up!

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