Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 days ago

Responsive Profile Card Component using Flexbox and CSS Grid

pure-css, accessibility
Carlos Alberto da Silva•280
@slayer-br
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 most proud of how closely I matched the layout and design, especially the responsive behavior and the clean structure of the CSS using custom properties. Next time, I would focus more on accessibility improvements, such as better semantic structure and ARIA labels.

(pt-BR): Tenho orgulho de ter replicado fielmente o layout e o design, especialmente o comportamento responsivo e a estrutura limpa do CSS usando variáveis customizadas. Na próxima vez, eu focaria mais em melhorias de acessibilidade, como uma estrutura mais semântica e uso de ARIA labels.

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

Positioning the avatar image partially overlapping the card header was a challenge. I solved it using negative margin and a white border to maintain the circular shape and separation from the background. Getting the background patterns to look good on all screen sizes also took some trial and error with media queries and background positioning.

(pt-BR): Posicionar a imagem do avatar parcialmente sobrepondo o cabeçalho do cartão foi um desafio. Resolvi isso usando margin negativa e uma borda branca para manter o formato circular e a separação do fundo. Fazer os padrões de fundo funcionarem bem em todos os tamanhos de tela também exigiu tentativa e erro com media queries e posicionamento de background.

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

I would appreciate feedback on my responsive layout decisions, especially the use of background images and how they scale at different breakpoints. Also, suggestions on how to improve accessibility for screen readers would be very helpful.

(pt-BR): Gostaria de receber feedback sobre minhas decisões de layout responsivo, especialmente quanto ao uso das imagens de fundo e como elas se ajustam em diferentes breakpoints. Além disso, sugestões para melhorar a acessibilidade para leitores de tela seriam muito bem-vindas.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,970
    @thisisharsh7
    Posted 3 days ago

    Awesome work! Your solution is clean, well-organized, and visually very close to the original design!

    Strengths:

    • The layout scales nicely across screen sizes — media queries and background positions are well-handled.
    • Good use of utility classes and CSS variables, which keep the code maintainable and scalable.
    • Avatar positioning with negative margin and a white border is a clever and clean solution.

    Some suggestions:

    • Semantic HTML: You might wrap the .card in an <article> instead of a <section> for better semantics, and possibly use <figure> for the profile image.
    • The footer attribution is nicely done but could benefit from aria-label="Attribution" to give it more context.
    • Folder structure: Since you’re using only one CSS file, there’s no need to place it inside a nested folder (assets/css/). You can keep style.css in the root for simplicity unless the project scales.

    Overall, solid execution — happy coding!

    Marked as helpful

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