Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

product preview using html and css

marina•50
@ladymarina08
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I did my best to stay faithful to the original layout but I know it wasn't, so please, if anyone can point out my mistakes, I'd be grateful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•6,770
    @R3ygoski
    Posted over 1 year ago

    Olá marina, bom trabalho, desculpa responder depois de 10 dias da postagem, seu projeto ficou fiel ao mobile.

    Mas notei que você não fez o design de Desktop. Isso ocorre porque você limitou a sua <section> class="mobile", no css você colocou pra que ela tivesse 375px, isso não era necessário, já que você poderia ter feito ela ter 100% ou 100vw (tamanho total da largura da tela) e só precisaria centralizar o resto do conteúdo. E para fazer esse alinhamento, você só precisaria usar a propriedade de display: flex no CSS.

    Quando vamos criar um projeto que é para celular, tablet, laptops, desktops e tv's, nós não fazemos eles pensando no HTML, o que fazemos é, criamos a estrutura no HTML de acordo, e quando vamos estilizar utilizamos o media query para que possamos definir como o projeto deve se apresentar em cada tela.

    E uma outra dica, evite ao máximo usar caracteres especiais no seu HTML e CSS, pois podem dar conflito no JavaScript, ou seja, não usar ~ (til), ç, ã,õ, sempre focar em escrever sem esses caracteres para que não tenha problemas futuros. Dessa forma: em vez de descrição usaria descricao, em vez de preço usaria preco, e por aí vai.

    Novamente, parabéns por ter feito um projeto que ficou fiel ao mobile, se precisar de ajuda com qualquer coisa, pode comentar aqui que eu tentarei ao máximo te ajudar com o possível.

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