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

Newbie - Card component

Pisca•55
@hliosdja
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm having trouble with the svg background for mobile view, I tried doing it with media query but it ended up messing the web page so i removed it.

My only question was, were there any other approach on how to do it on mobile view to look like the one provided on the design? or is it even good to apply those SVG background via CSS and not on the html? This is my first time using an SVG for making a web page and I'm also still a newbie as a frontend so i was a bit confused on how to do it.

It's a real fun doing the challenge and I'm looking forward to the next one.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shivam•520
    @shivjoshi1996
    Posted over 4 years ago

    Hey there!

    Awesome attempt on this challenge.

    For the SVG background, instead of using units like 100px, try and use units that are relative to the viewport (vh, which is the viewport height, and vw which is the viewport width.

    For example, if you replace what you currently have with background-position: right 50vw bottom 40vh, left 50vw top 50vh; , then the circles should look a little better on mobile and desktop, because they're moving depending on the size of the actual screen.

    You can then add a media query and tweak those units around so that it looks good on mobile and desktop, but you may not need to. Also, adding an SVG using CSS is perfectly fine (especially if it's just for decoration purposes and does not have any functional impact to the page).

  • Efosa Collins EVBOWE•365
    @efecollins
    Posted over 4 years ago

    Speaking of which, the comments above concerning the SVG should help but the NAME, AGE and Number of followers, blah, blah. You should make it less bold than that.

    Doing this will make it look less painful and sharp to the eye

  • jul_julham•210
    @zulhamsy
    Posted over 4 years ago

    Hi! Great work!

    I'm newbie too xD, but maybe some advice would help :D

    I think whether you using 'background' props via css or directly using img tag on html, the result will still be good and still a valid html, but for me I prefer using img tag since it would be easier to 'position' it using absolute props

    btw keep your great work!

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub