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

Qr_Code with HTML & CSS

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

Solution retrospective


Is the architecture of my code better than my previous project (card_preview) ?

I don't really know how to adapt the width of my page to the screen, could you give me some advice please ?

Is there any bad habits on my code ?

Thanks for your feedbacks ! I understand really quickly thanks to you !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,890
    @AdrianoEscarabote
    Posted almost 3 years ago

    Hi @LucatoNine, how are you?

    You did a great job on this challenge, but I have a few tips I think you'll like:

    1- Page should contain a level-one heading, you could have changed h3 to h1 click here

    2- Document should have one main landmark, you could have put all the content inside the main tag click here

    for the project to have a better responsiveness I made some changes:

    body { max-width: 265px; width: 100%; }

    .pict { max-width: 240px; width: 100%; }

    The rest is great! Hope it helps... 👍

    Marked as helpful
  • Krzysztof Kondracikowski•280
    @Chris-ai
    Posted almost 3 years ago

    I have small advice about fonts. You can import them just with one link in your html. Look here

    Also wrap your code in some containers. Not let them just be mess in <body>.

    For example:

    <container>
    ... your code ...
    </container>
    
  • Mohammad Zaid•580
    @them7d
    Posted almost 3 years ago

    you can use

    width:100%; and height:100hv;

    or width:100vw; and height:100hv; on body

    to adapt width and height page

    in additional move style of html to the body and style body to div contain (img,h3,paragraph) check html code this page: https://them7d.github.io/qr-card

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

Oops! 😬

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

Log in with GitHub