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

Profile Card Component

Keven Molina•60
@Kmolina009
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, this is my first challenge. I have the elements placed in the right position for the desktop requirement, but I'm having issues with the mobile media-query. Will be refactoring in the meantime.

Any feedback is very much appreciated, Thank You.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Milton Chung•465
    @MiltonChung
    Posted over 4 years ago

    Hi Keven! First of all, nice use of semantic HTML and meaningful class names! Your card looks pretty nice but one thing that could be improved on is the spacing and the font sizes of your profile stats. I used justify-content: space-evenly; in the stats container so that each stat is evenly spaced in that space, but you can play around with different properties. For your mobile media query, there's really not much for that besides anything less than around 400px, but for your case, your background circles are what's making the website a little funky. I suggest you to put the background images in your body css like this:

    body {
            ...
    	background-color: $dark-cyan;
    	background-image: url("./images/bg-pattern-top.svg"), url("./images/bg-pattern-bottom.svg");
    	background-repeat: no-repeat, no-repeat;
    	background-position: right 50vw bottom 50vh, left 50vw top 50vh;
    	overflow: hidden;
    }
    

    so that it doesn't stretch out your website! You can always check out what I did in my profile

    happy coding!

  • Account deletedPosted over 4 years ago

    Hi Kevin i have nothing to say Milton Chung already said the important thing overall you great and keep 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
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