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

landing page used html and css only

Anthony Guilherme•190
@oAnthonyG
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedback welcome. I still think there are things to improve and I'm not really sure if it's working perfectly on all platforms

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Luciano Lima•1,270
    @LucianoDLima
    Posted about 3 years ago

    Boa mano!

    O que tu pode fazer pra melhorar seria ao invés de usar <div id="container-card"> tu pode trocar por <main> que é a semântica correta para o conteúdo principal da sua página.

    Pra centralizar a página de forma correta (vertical e horizontal) tu pode primeiro remover o padding-top: 80px do seu <div id="container-card">, ai tem duas manerias boas pra seguir, que seria com grid ou flexbox, tu escolhe.

    -Com grid: Vai no <body> e adiciona -> display:grid; , place-items:center. Isso vai centralizar seus itens na tela.

    -Com flexbox: Ainda no <body> adiciona: display:flex; , flex-direction: column; , justify-content: center; , align-items: center. Isso vai deixar tudo no centro da tela, independente do zoom, e o flex-direction:column vai deixar um embaixo do outro ao invés de um do lado do outro o seu <div class="attribution">

    Marked as helpful
  • Abdul•8,560
    @Samadeen
    Posted about 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="container-card"> instead of <div class="container-card">.
    • And your footer should be <footer class="attribution"> instead of <div class="attribution">.

    This should fix most of your accessibility issues.

    -You can use flex or grid to center your container horizontally and vertically.

    . Regardless you did amazing... hope you find this helpful... 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 1st-party linked stylesheets, and styles within <style> tags.

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.

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