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

Beginner "Barebones" HTML/CSS use

Sarah Kessler•50
@serakay
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 add the .svg files as background without accidentally removing the background colour. As you'll see, I just added the images in html and then fidgeted(?) around with positioning and z-index to achieve a similar look. I looked at the solution code provided and saw that url(img.svg) format was used but when I tried it, it did not work.

My mobile version might be a bit wonky since I'm still working on responsive design skills.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Web Frog•1,840
    @MasterDev333
    Posted over 4 years ago

    Hi, @Sarah. Great work. It would be better if you use background-image for body tag or some pseudo elements. In this challenge, positioning background circles are little tricky, hope you solve it right way. Here's my solution if you'd like to check. https://www.frontendmentor.io/solutions/profile-card-xRCu-QVRG Happy coding~ :)

  • Aleksandr Aksenov•750
    @axevldk
    Posted over 4 years ago

    Hi, @Sarah Kessler ~ Good work so far. Here are my opinions for your question.

    You can use pseudo elements for the background-image. It is much better to use in such cases.

    Here is a link to my solution. Hope this will help you even a bit. Happy coding ~ ✨

    https://www.frontendmentor.io/solutions/profile-card-component-2n53OyvZb

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