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

html and css - profile-card-component-main

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

Solution retrospective


Any feedback on the css? For some reason I wasn't able to give 100% concentration to following a strict flex box dev, so I ended up just hacking the css. Overall I was able to complete this in under an hour, however I just realised that I forgot to add the background circle elements. The positioning of the image wasted a lot of my time and I ended up forgetting about the background elements while I was trying to complete the challenge for time.

Im not sure why there is the big white space at the bottom of the card. I have a feeling it is because I shifted the profile image upwards, however I haven't been able to get rid of the white space, any ideas to solve this?

Also is it possible to use flex box and have the profile image in the position that it is? I was not able to achieve this so I ended up butchering my css. Hopefully another shot down the line and I can improve this and not forget the background circles :).

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • H0bG0blin9g•55
    @H0bG0blin9g
    Posted over 3 years ago

    I had a "quick" go at getting the background circles, but I can say that it was not easy as it took me atleast 30 mins to have something reasonable albeit off. This clearly shows the need to look into the various ways of positioning of elements.

    I will look at the solutions from the other member, but would appreciate any insights into where I made a mistake in the positioning of the circles.

    also what would be the best fix for the errors that appear? Is it wrong to put a <section> inside of a <main>? (it must be since it has produced an error right?! lol)

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