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

QR Scan Page using HTML and CSS

ItachiCodes•160
@itachidevs
A solution to the QR code component 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? Iam proud of this HTML code
 
    
      
        
      
      
        
          Improve your front-end skills by building projects
        
          
            Scan the QR code to visit Frontend Mentor and take your coding skills to the next level
          
          
          
      
    
  
What challenges did you encounter, and how did you overcome them?

Durinng the project completion I have encountered a problem with the layout of the page. I tried to revise the topic of CSS flexbox to overcome this problem.

What specific areas of your project would you like help with?

Is it can be developed in the area of the background container?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,790
    @danielmrz-dev
    Posted over 1 year ago

    Hey @babybhavani!

    Your solution is really impressive!

    I've got a couple of ideas (about how to use HTML better) that could make it even stronger:

    📌 First: Think about using <main> to wrap your main content instead of <div>.

    Imagine <div> and <span> in HTML as basic containers. They're good for holding stuff, but they don't tell us much about what's inside or its purpose on the webpage.

    📌 Second: Consider employing <h1> to <h6> tags for headings rather than using <p>.

    The <p> tag is primarily intended for paragraphs. When it comes to headings, HTML offers us a range of heading tags: from <h1> to <h6>.

    Here's a quick guide on how to use them:

    • The <h1> to <h6> tags are used to define HTML headings.
    • <h1> is for the most important heading.
    • <h6> is for the least important heading.
    • Stick to just one <h1> per page – it should be the main title for the whole page.
    • And don't skip heading levels – start with <h1>, then use <h2>, and so on.

    It's more than just text size — it's about structuring your content effectively.

    These tweaks might not change how your page looks, but they'll make your HTML code clearer and help with SEO and accessibility.

    Hope that's helpful!

    Keep up the great work!

    Marked as helpful
  • Alyfer Jacobsen•450
    @AlyferJT
    Posted over 1 year ago

    Hi there!! Well, that problem of yours is not something that is related to Flexbox. Before all, congratulations, you did a great job on centering and organizing the boxes in the project...

    You can use the body in your advantage! In that project, when you don't need to roll down to see other things on the screen, you can set the body as your unique background.

    For example:

    body {
        width: 100%;
        height: 100vh;
    }
    

    The width: 100% will let the body fix at the 100% of the page width, as it is it's only parent And the heigth: 100vh will let the body fix at the 100% of the View Heigth (vh)

    And another thing that i saw, it's the white borders on you project, you can fix that by setting the default CSS to another value

    Every navigator has an default CSS value, so you need to change that on your on CSS files

    you can do that by using this, at the very top of your CSS:

    * {
        margin: 0;
        padding: 0;
        box-sizing: border-box;
    }
    

    to understand what is margin, padding and box-sizing, you'll need to search about the box-model

    Well, i hope that you get that as an information for looking for the answers, this is just to you to know that this exists, and you have to understand that to improve your designs.

    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 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