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

Profile Card Component Solution

Ritam Mishra•30
@ritam-mishra
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was a tough challenge and I tried to do it as simple as possible.

Can suggest whether it is a good practice to use <span></span> tags inside <p></p> tags and then changing the style of the spans separately? (you can see I used span for 26, London, followers, likes and photos and then changed its color separately) Can it be done or is there's an alternating way, please suggest.

I would request everybody to go through my simple code and please correct any error if you find. And you are free to give any feedbacks, which I will accept wholeheartedly.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Azan•140
    @Azi-01
    Posted over 3 years ago

    Hi, Good job on the solution! It looks nice and pretty close to the design. I checked out the site and your code, and noticed some things, so I would like to give a few suggestions. First, I noticed that the profile image and the white border around it has a gap and the background is leaking through it. Try replacing border: 5px solid white; with outline: 5px solid white; in .profile-pic img rule set. Second, try wrapping all the content in <main> </main> tags and use <div> to group different things together.

    I hope this helps! and again well done on the solution :)

    Marked as helpful
  • Ritam Mishra•30
    @ritam-mishra
    Posted over 3 years ago

    Haha, I knew I had this bug. The background was leaking a bit. Thanks for the solution. I'll change it. Very much thanks.

  • Naveen Gumaste•10,420
    @NaveenGumaste
    Posted over 3 years ago

    Hello Ritam Mishra ! Congo 👏 on completing this challenge

    Let's look at some of your issues, shall we:

    • Always use h1 first and then h2, h3 and so on

    • Wrong font-weight for the number in bottom

    happy Coding😀

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub