Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Blog Preview Card Solution - HTML - CSS

Caio Lopes Silva•70
@CaioLopes5556
A solution to the Blog preview card 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?
  • Gostei de como ficou o box-shadow do card, estava em dúvida se utilizaria apenas essa propriedade ou se teria que unir com alguma outra para criar aquele efeito. No final percebi que era uma união entre box-shadow e border: 1px solid #000

  • Ainda estou entendendo o uso de variáveis no CSS, sei da importância pra manter a manutenção do código, mas imagino que para esse projeto em si não era tão adequado, por ter poucas linhas para alterar.

What challenges did you encounter, and how did you overcome them?
  • Utilizar o REM como unidade de medida foi um pouco complicado, não pelo calculo de conversão em si, mas saber onde utilizar. Teve um momento que me perguntei se era realmente uma boa ideia utiliza-lo no width de alguns elementos.

  • No fim fui fazendo testes trocando o font-size do navegador, e percebi que todos os elementos mudavam de tamanho, oq me tranquilizou.

What specific areas of your project would you like help with?
  • O que me preocupa um pouco é a organização do código, sinto que utilizei muitas classes e não sei se a maioria era realmente necessária. Também não sei se está semântico o suficiente, quase pensei em utilizar a tag <figure> para a imagem do card, mas optei apenas pela <img> no final.

  • Talvez eu esteja caçando erro, mas quando eu do um Zoom muito alto no site, o Footer acaba ficando "preso" no meio dele ao descer a pagina.

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 Caio Lopes 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.