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

Mobile first, responsive with pure CSS

Gabriel Monsalve•320
@Gabrieldev-web-coder
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I don't use SASS or other preprocesser, because for the "newbies" the most important is dominant the basics of lenguajes (and because i don't know use it yet xD)

I try to do this responsive, and i said "try" because i think there are better methods than i use in this case, if you know how to better i'll thank give me feedback <3

My bigest problem was the background with the position background and the porcents, that made me write a media querye for each misalignment, and repeat code for change a single value :/

All other, if you see something you think can do better, please write it!

Be severe, is the way to learn. Thanks!

(Sorry if my english make you cry, i'm learning)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Samuel Palacios•615
    @samuelpalaciosdev
    Posted over 4 years ago

    Hi, ippo👋

    Well done on this challenge! Your solution looks good👍

    I only suggest some things 😉:

    • You don't have a h1 on this project as it stands. Headings provide valuable information by highlighting important topics and the structure of the document. For this project, I'd set it where is the person's name.

    • There're too many Media Queries on the background position. I'd think you should see others solutions to see how they approach that, because too many media queries are not the best approach I think.

    I hope this would help you, have a nice day, keep coding!💙

  • Marwan Tamer•45
    @MarwanT-dev
    Posted over 4 years ago

    you can give the circles width and height with vh and vw instead of pixels to make it responsive or if you want to use media queries you can use these: @media(max-width:767px){} @media(min-width:768px){} @media(min-width:992px){} @media(min-width:1200px){} those will fit all screens

  • drallas•375
    @Drallas
    Posted over 4 years ago

    Si, tu ingles me da los ojos lleno de lágrimas :) Pero si te querrás escribir mejor ingles, puedes considerar usar Grammarly.

    There are too many Media Queries and the background is not scaling good and blanks out for me.

    I have not done this challenge myself yet, but i recommend looking at other peoples solutions. You have submitted a solution so previous ones are unlocked for you!

  • Gabriel Monsalve•320
    @Gabrieldev-web-coder
    Posted over 4 years ago

    A lot media queries background position fixed.

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 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

Oops! 😬

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

Log in with GitHub