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

Responsive NFT preview card using Flexbox and CSS variables

pure-css, semantic-ui, accessibility
Carlos Alberto da Silva•280
@slayer-br
A solution to the NFT preview 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 the semantic structure and the responsive layout I achieved with a mobile-first approach. The use of CSS custom properties helped keep the styling clean and maintainable. Next time, I would improve the hover interactions by adding smooth transitions and explore using a CSS overlay icon for the image hover state, just like in the original design.

(pt-BR) Tenho orgulho da estrutura semântica e do layout responsivo que consegui com a abordagem mobile-first. O uso de variáveis CSS ajudou a manter o estilo limpo e fácil de manter. Da próxima vez, eu melhoraria as interações de hover adicionando transições suaves e exploraria o uso de um ícone sobreposto com CSS para o efeito hover da imagem, como no design original.

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

Creating the hover overlay effect on the NFT image using only CSS was one of the most interesting challenges. I had to combine ::before and ::after pseudo-elements to simulate both the colored overlay and the view icon, then control their visibility with smooth transitions. Another small challenge was keeping the icon and text in the pricing section vertically aligned — Flexbox with align-items: center and gap provided a clean and efficient solution without relying on any positional hacks.

(pt-BR) Criar o efeito de overlay com hover sobre a imagem do NFT usando apenas CSS foi um dos desafios mais interessantes. Precisei combinar os pseudo-elementos ::before e ::after para simular tanto a sobreposição colorida quanto o ícone de visualização, controlando a visibilidade de ambos com transições suaves. Outro pequeno desafio foi manter os ícones e os textos na seção de preços alinhados verticalmente — Flexbox com align-items: center e gap ofereceu uma solução limpa e eficiente, sem precisar de gambiarras de posicionamento.

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

I’d appreciate feedback on how to best implement the hover overlay effect on the main image using only CSS. Additionally, suggestions on improving accessibility and keyboard navigation would be welcome.

(pt-BR) Agradeceria sugestões sobre como implementar o efeito de overlay com ícone sobre a imagem principal usando apenas CSS. Além disso, sugestões para melhorar a acessibilidade e a navegação via teclado seriam muito bem-vindas.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Carlos Alberto da Silva'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
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.