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

Profile Card (HTLM, CSS)

Lucas Laino•70
@l-laino
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, I'm trying to get serious about learning web development. There are some things that I'd like to do better in the viewport, it just doesn't look right on mobile. Should I start a site from mobile and then scale it to a browser? I'd like to hear (read) everything that I could do better. Thanks for the attention.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Samyr Oliveira Ribeiro•215
    @SamyrOR
    Posted over 4 years ago

    Hello @l-laino, its look good at all, but somethings a think can be better, for best pratices you could put all colors that you will use, on variables of css, putting this on :root {}, this help in the maintence of the code (possible to put common sizes too and other things), matching all colors with the recived style guide , and for the bottom status under the numbers, you could space it with "letter-spacing" property.

    At the mobile, i would add more margin on top to center the card, and match the font-sizes to better view with media queries.

    The Mobile First aprochion, is a thing that i'm learning and loving it, you can code the entire site to mobile, and then with media queries just scale, this is much more easier, confortable than just try to make it fit on mobile, you could give a try, and look for mobile first.

    I expect that i have helped in something.

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hello there, Lucas Laino! 👋

    I just wanted to say, congratulations on completing your first Frontend Mentor challenge! 🎉 Well done on this one! 👍

    Simply follow the helpful suggestions given above, and I think you'll be good to go! 👍

    Keep coding (and happy coding, too)! 😁

  • Abhik•4,820
    @abhik-b
    Posted over 4 years ago

    Hi Lucas, You have done a great job on this challenge , background circles are responsive and your card looks cool!

    I guess if you reduce the font-size a bit and try mobile first approach (which I'm told is the industry best practice) then your solution would have been amazing !!

    Happy coding 😇 and Keep contributing these Great solutions 🚀

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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