Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Profile card component

accessibility
Aayush Kumar•110
@AK-CHP1
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I couldn't figure out how to find the correct box-shadow value, and background-position for images. Please help me with this. Any other improvement feedback or suggestion is appreciated.

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rajaul Islam Ratul•1,250
    @ratul0407
    Posted almost 2 years ago

    Hey coder🚀🚀

    Congratulations on completing this challenge🎉🎉🎉. The solution is pretty good. Onto your question,

    • For the background images instead of using percentages background-position: -50% 180%, 160% -150%; ,You can use vw and vh something like this,
    body {
      background-position: right 50vw bottom 40vh, left 50vw top 50vh;
    

    Now the problem with using percentages are that they would not behave as you want if the viewport changes a little bit as they are hardcoded. But with vh and vw no matter what the screen size is they will always be visible and stay in the same place as they are relying on the user's view height and view width.✌

    • And for the box-shadow, there is hardly any box-shadow in the design. Maybe a little bit of shadow around the corners. Now to achieve such a small thing you have to play around with a lot of numbers (blur radius, spread radius etc....) and it is a little painful. So why don't you use a box-shadow generator to reduce the pain a little bit. Like this one or maybe this one

    I hope it was helpful for you👍👍

    Happy coding brother🙂🙂

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