Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

QR code component using Flexbox

Madeha•10
@Maadeha
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 was most proud of me using flexbox, but next time I would try to get into media queries

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

Knowing which element to use flexbox.

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

Any help is welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alyfer Jacobsen•450
    @AlyferJT
    Posted 10 months ago

    Hi there, nice job! Just a little tip about the flexbox, you don't really need to set a justify-content or align-items everytime you use display: flex; on a container. The main goal of the flexbox is that you have the control of the elements inside your container, so you make then to behave the way you need.

    Well, in my view, this would be something i would do in that specific project.

    I would change the HTML to:

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

    Using a <div> around <h1> and <p>, you would have a better control of the element.

    So you would have 2 elements inside the .container

    So in the CSS you have this:

    display:flex;
    flex-direction: column;
    justify-content: center;
    align-items: center;
    

    that's not wrong in all cases, but in that one, you could do this:

    display:flex;
    flex-direction: column;
    justify-content: space-between; /* i think this would be better */
    gap: 2rem; /* or whatever value you want */
    
    padding: 1rem; /* i think that a fixed value would show a better look, but depends*/
    

    The gap is a space between the elements inside the flexbox

    So doing all that would remove the weird blank spaces around it, and bring it a nice look. I recommend you to search a fun minigame that calls Flexbox Froggy on google, this somehow teachs you the logic behind the flexbox. Overall, i think tha's it, if you didn't understand something, feel free to ask :D

    Marked as helpful
  • MElhatmi•40
    @MElhatmi
    Posted 10 months ago

    You have done well using semantic html, properly centering the qr container using flexbox. I'm getting the impression that you are too concerned with responsiveness already, from my understanding of the design all we need to do in regards to responsiveness is that we center the container across all screen sizes, and you already to that. what I advice you to do now is to get familiar with figma and how to get all the metrics, and just copy all the values from widths and heights to margins to font sizes to border radius and even the box shadow. until you are close enough to the design after that I advice you to take an optional step to learn about css variables and implement them in your solution, they maybe overkill for a small project like this but i think its a good practice going forward

    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