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

flexbox, html, css

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

Solution retrospective


  1. I had a hard time designing the circles as displayed in the example. I would love for someone to assist with the solution

  2. I choose the mobile version however I feel the sizing reflected that of the desktop version. Please provide feedback.

I am in the baby stages of learning HTML and CSS. I decided to try this project as I feel the best way for me to learn is to be hands on. The project is not perfect but its done. On to the next newbie challenge :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • jjjayed•270
    @jjjayed
    Posted over 3 years ago

    Hey there! Congrats on your first project. Just a couple of things to address.

    1. A lot of the issues you have right now is because of the lack of responsiveness, that's why the design is strictly for mobile. I highly recommend reading up on responsive web design and using @media queries.

    2. I also noticed that your fonts aren't working because you need to put font-family: Kumbh Sans The plus sign is not needed for the CSS part.

    3. Lastly, a cool trick. Surround the "26" text with a span tag, while still being inside the h1 tag. You can then select that span tag in the CSS and change its font weight to 400.

    Hope this helps.

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