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

Profile Card Component using Flex & Grid w/ Translates

vite
Gabriel Montplaisir•210
@GabrielMontplaisir
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Setting position: absolute on the circle images (For the avatar picture & background circles) and transform: transition() them to the appropriate spot did the trick. However, I'm having a hard time to match them in their mobile version. I have a feeling it may be fixed using clamp(), but would have to play with it some more.

Let me know if you have any feedback!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alamin•1,980
    @CodeWithAlamin
    Posted over 2 years ago

    Hi Gabriel Montplaisir👋 Great job on completing this challenge! 🥳

    Here are a few specific tips and suggestions for creating a responsive design that works well on mobile devices:

    • Keep the layout simple and focused on the most important content and features. On small screens, it's important to prioritize the content that is most valuable to your users, and to make it easy to access and use.

    • Use a mobile-first approach, where you design for the smallest screen size first and then add styles for larger screens as needed. This can help you ensure that the mobile version of your site is optimized for small screens and touch-based interaction, and can make it easier to create a cohesive design across devices.

    • Use responsive images, by using the srcset and sizes attributes on the img element or the picture element with the source element. This will allow you to serve different versions of an image at different resolutions, depending on the size of the viewport and the pixel density of the device.

    • Use touch-friendly design elements, such as larger buttons and clickable areas, to make it easier for users to interact with your site on mobile devices.

    • Test your design on a variety of mobile devices to ensure that it looks and works as intended. This can help you identify and fix any issues that may not be apparent on desktop screens.

    By the way, this is a well done solution to the challenge. Great job!

    I hope this feedback was helpful. 😊 Keep up the good 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