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

Presentation Box

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

Solution retrospective


I find it difficult to set up the background. Any feedback would be appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hi! Lorenzo, I think it my second feedback and I would say good work you did it according to what were required in the challenge, but I have suggestion.

    I saw that you only implemented the media query for 375px . It is ok you did not do anything wrong. But keep in mind there are hundred thousand people are here on this platform. All have mobile, desktop or laptop. Suppose 10 people saw your design / website including me. suppose I have android mobile phone (actually I have) of screen width 375px and other have 360px 320px or above 400px screen-width phone. out of 10 only me will appreciate your work and will come back to your website again and rest other will never come back because of bad user experience.

    So what I am pointing out till now is USER EXPERIENCE, always make your design UX better so that more and more people come and majority of people re-visit again.

    I hope you understand.

    Good Luck

  • Hania B.•1,280
    @techanthere
    Posted over 3 years ago

    I solved this problem using background-position: right 50vw bottom 40vh, left 50vw top 50vh; You will need to set the image as background in body.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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