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

HTML and CSS with flexBox

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

Solution retrospective


Hi,

Second challenge with HTML / CSS abd Flexbox. Not easy to place the circels !

Thx to everybody who let a feedback :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • KonradOlech•55
    @KonradOlech
    Posted about 4 years ago

    Hi, my advice is deleting max-width attribute from .container, because it is messing with styling in wider screens (4k displays are more common every year) and it is unecessary.

    I would move "circles background" from .container and merge it with body bg. In hypothetical situation when you decide to move/delete/change profile card component your solution will change bg of website.

    Third advice - to fix this blue line between img and border (on person photo) add "background: #fff" attribute on img. It is caused by bad anti-aliasing on svg render so this way you cover it.

    Anyway - good job, very similar to my solution :D

  • Elise Rousseau•685
    @SarahHenriette
    Posted over 4 years ago

    Hi Studio Webpic , 🙂

    Well done because it's really well done and the visual is almost identical 👍

    yes I agree enough to place the circles it is not obvious, I had also had a little trouble especially on the mobile

    Good continuation

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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