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

css, flexbox, media queries, javascript, multiple background images

Marc Neumann•60
@NewMeeDev
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there,

feel free to analyse and use my code. Feedback is very welcome.

Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • darryncodes•6,350
    @darryncodes
    Posted over 3 years ago

    Hi Marc,

    Really great solution, nice one!

    • you might want to consider moving all your background declarations from the .wrapper class and adding them to the <body>. There is a white border round the whole design at the moment.
    • you could also clear up your accessibility report if you swapped <div class="wrapper"> for <main class="wrapper"> and <div class="attribution"> for <footer class="attribution">. Semantics is really important
    • your design should only have one <h1> consider changing the rest to <h2> here is some info

    Keep up the good work!

    Marked as helpful
  • Web Wizard•5,690
    @rsrclab
    Posted over 3 years ago

    Hi, @NewMeeDev ~

    Congratulate on your solution to FM challenges. I have studied your work, and it seems great. I have learned a lot from it. Here are some of opinions on this project.

    1. Limiting background image to wrapper doesn't look good. I think making background image fill whole screen could be better in this case.
    2. Limiting card width is necessary, but I recommend to use max-width instead of manually setting width constant.
    3. I recommend you to try using BEM structuring for classing elements. That could be big advantage when you are stuck with bigger projects.

    Hope my words can help you even a bit. Happy coding ~

    Marked as helpful

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