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

Simple QR code page using flexbox.

Lyle Patterson•60
@Squing0
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?

I'm proud of how quickly I was able to complete this project.

What challenges did you encounter, and how did you overcome them?

Mainly positioning of elements.

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

I would definitely change how I centered the main section to be more dynamic.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted about 1 year ago

    Hey @Squing0!

    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 using <h1> for your main title instead of <h2>.

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

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

    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
  • Bernardo Poggioni•6,990
    @R3ygoski
    Posted about 1 year ago

    Hello Lyle, congratulations on completing your project! It's very well done and closely resembles the proposed design.

    I noticed that in your footer, there are two <p> tags with text. They don't need to appear there; you can delete those <p> tags and leave only the div.attribution.

    Regarding your alignment approach, it's not incorrect, but you missed using some properties on your body tag, such as justify-content: center; and align-items: center, which would help center your card. Then, you can remove the margin: auto; from your div.mainSection.

    Another tip I'd like to give is about using semantic HTML. Your HTML structure is well done, but it lacks some semantics. For example, your div.imageContainer could be a <figure>. Semantic HTML like this significantly improves the accessibility of your project.

    Another tip, but this time regarding CSS, is when working with measurements, spacings, and font sizes. It's strongly recommended to use the rem unit because it can adapt to the user's font settings and provide responsive expansion or contraction of your element.

    Again, congratulations on completing this project so closely to the proposed design! Keep practicing and improving. If anything I said isn't clear, please ask below, and I'll try to help as best as I can.

    Marked as helpful
  • Sivaprasath•2,500
    @sivaprasath2004
    Posted about 1 year ago

    Hello, I would like to extend my congratulations on completing this challenge.

    • I will give some suggestion i believe its used for improve your solution result.
    • In HTML You will use the following tag omit the codes.
    <footer class="footerSection">
      `THIS IS SPOILED YOUR SOLUTION
    
    <p>Improve your front-end skills by building projects</p>
      <p>Scan the QR code to visit Frontend Mentor and take your coding skills to the next level</p>
    
    OMIT THIS 2 <p> tag's`
    </footer>```
    
    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

Oops! 😬

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

Log in with GitHub