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

QR code

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

Solution retrospective


  1. How can I improve the html structure (semantics) ?
  2. How to center the main element vertically besides using the fixed value (i.e. I use margin: 12em auto)? Maybe with percentage/vh or using position as I think hard-coded value is not good
  3. Should I use flexbox in this example?
  4. Should I implement BEM/OOCSS or Sass from now on for better organization?

Thanks for reading.
Any advice would be greatly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • BRIVAL-M•60
    @BRIVAL-M
    Posted almost 2 years ago

    Hi :) For semantics, you can use the HTML tag <figure> to code your card.

    More about this tag

    And here is an image explaining the BEM, but you already know :) BEM tips img

    Marked as helpful
  • Luis Jimenez•760
    @LuisJimenez19
    Posted almost 2 years ago

    Hi, congratulations on finishing the challenge.

    You are correct there is a better way to center it. A tip is that whenever possible it is better to manipulate the content from its container. You can do this:

    body {
        flex-direction: column;
        min-height: 100vh;
        display: flex;
        background-color: var(--bg-color);
        justify-content: center;
        align-items: center;
    }
    

    This will center everything perfectly. I see that you use <main> to make the card, which is fine but would be better:

    <main>
    <div class="card" >
        <img src="images/image-qr-code.png" alt="qr-code">
        <h2>Improve your front-end skills by building projects</h3>
        <p>Scan the QR code to visit Frontend Mentor and take your coding skills to the next level</p>
    </div>
      </main>
    

    and in this .card give it the styles of the card, and if what you want is to leave the footer below you can apply to the main a ``flex-grow:1;

    I hope my contribution is helpful.

    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