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

html, css, flexbox solution

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

Solution retrospective


Hey mentors, I got so much helpful feedback for my first attempt with this challenge, I adopted it all and learned so much! Thank you all so much for this, especially @AgataLiberska and @grace-snow! 🥰 I took notes and will use them in following projects! I'm really happy about the improved responsivness! Here is my updated solution. It is still the same link, so the old version might be still stored in your browser, reloading is not enough to solve that. I opened it in another browser. 🤷‍♀️ One thing bugs me: There is a thin line inside the border of the image where the background shows. Has anybody an idea for that? Happy coding, Linda 😊

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 4 years ago

    This is great for 1 week in, well done! Here are my tips to improve:

    • Instead of a large margin-top on your card, just have a little padding on the outer wrapper (in this case the body element) so content can't hit the sides. Give that body a min-height of 100vh and the card will be centered on the scene
    • Don't forget details like box shadow on the card. There are some good box shadow generators out there that can help you get it looking right
    • On card background, you don't need width. It's a block element already. Instead of height in percent, try a min-height in rem
    • Similar for the card. You don't need to give it width or height. It will be more easily responsive if you give it width 100%, and a max-width of whatever in px/rem. That will let it shrink down for small phones. Height is not needed.
    • Alt text is a good effort on Victor's image, but waaaay too long. Just Victor Crest is fine. It's an image of him, that's all the info we need to know.
    • If you want to horizontally center with margin, you can do that with margin left and right set to auto rather than a pixel value
    • You're relying on default margins on elements for vertical spacing at the moment. That means your solution will look different in different browsers. Consider adding a modern css reset to remove all those defaults, then add vertical margins to elements as needed (top tip - it's often more manageable if you add margins in one direction mainly, like margin top on each paragraph, heading etc, rather than setting both directions)
    • The stats section needs semantic HTML adding. You never want to have text in spans/divs alone. Try swapping container-rates for a ul, then each child within it can be an li.
    • I think you've set align items and justify content the wrong way around on that container-rates element too - maybe check that.
    • remove the brs. Use CSS to set elements to display block instead
    • Add text align center to the stats. I'd also remove margin from them or at the very least use the same class on all three of them.

    Keep on going - that's loads of suggestions for you to be looking up 😂. Just take your time and learn step by step. Good luck 👍

    Marked as helpful
  • Account deletedPosted about 4 years ago

    Hello , ellienndea

    Congratulations on completing your first challenge. Your solution looks good 👏

    Have fun coding.

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    Good Job so far but I would try to work on your styling for your horizontal line. Otherwise good start to this challenge

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.

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

Oops! 😬

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

Log in with GitHub