Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

Profile Card Component with Sass

sass/scss
IO•720
@i000o
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud of my sustained ability to replicate design briefs with a sharp eye for detail. I thank my art/design background.

This one had a bit of friction for me. There was some mind-boggling moments with the body being flex: row; and the card (section) being flex: column;. I had particular issue with the background images flexing with the viewport, the profile icon positioning and weirdly, the positioning of the footer as well. Normally, I've found these card layouts easier than this one.

Taking breaks and stepping away helped me push through. Sometimes perceptibly 'big' problems can be resolved with only a few lines of code. You just need to specify the problem to yourself rather than thinking of it as being 'broken' or 'not working' when you might be 75-80% there.

What challenges did you encounter, and how did you overcome them?

background-image: It was frustrating that these SVGs flexed when the viewport was adjusted, as this changed the design and I'd constantly have to reposition the circles according to X/Y values with background-position properties and I didn't enjoy this. I don't know what the best way to work with SVGs is.

For now, I've marked new positions at breakpoints but the images don't 'flow' into their size as much as I'd like. They kind of snap. This is the best I can come up with right now.

What specific areas of your project would you like help with?

If anyone knows a better way to have the bg images proportionally resize compared to the viewport without changing their position in relation to the card, that'd help me. I almost wanted to 'pin' them to the corners of the card. But instead it seemed that with every position change, the size would also change and vice versa, so it felt annoying to grapple with. Should I have used specific pixel units in background-size instead of contain? Should I have only adjusted background-size instead of the position values?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on IO's solution.

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.