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

Landing page com html5, css3 e flexbox.

Thais Duque•30
@Duquewdev
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Olá, pessoal!

Comecei a realizar desafios há pouco tempo e não tenho certeza se estou indo bem.

Com base no desafio enviado...

O que preciso melhorar? Em que preciso focar?

Agradeço qualquer feedback construtivo!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Fala Thais, tudo bem? Parabéns pelo desafio!

    Sua solução ficou mto boa, a única coisa que eu mudaria é a estrutura do HTML, limpando um pouco o código tirando algumas divs. Por exemplo, você pode segurar todo conteúdo em um bloco só usando (<main> ou <div>) nesse caso vamos usar <main> por que é uma tag semantica. Se você notar, nem precisa adicionar nenhum div além da principal pra segurar o conteúdo (img, h1 e p). A estrutura ideal e mais limpa possível pra esse desafio é essa aqui:

    <body>
    <main>
    <img>
    <h1></h1>
    <p></p>
    </main>
    </body>
    

    Depois me diz se foi útil 😎

    👋 Espero ter ajudado e continue no foco!

  • Jorge Muñoz•240
    @jlmunozfdev
    Posted almost 3 years ago

    Creo que tienes un exceso de div's, al principio cuesta no utilizarlos, pero te vendría bien utilizar HTML semántico para engoblar ciertas cosas, por ejemplo quedaría más o menos así:

     <section class="container">
       <div class="div__card">
            
            <img src=".assets/image/image-qr-code.png" alt="qr">
    
             <h1 class="card__title"> Improve your front-end skills by building projects</h1>
    
              <p class="card__paragraph">Scan the QR code to visit Frontend Mentor and take your coding skills to the next level.</p>
            
       </div>
    </section>
    

    Puedes ayudarte de este artículo que te dejo aquí sobre HTML semántico. Que estés bien.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub