Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 24 days ago

Responsive page using flexbox

Leonardo Vandes•90
@ChessUP
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?

Even though it's something so basic, I'm happy to be able to complete it, even though it might not be how a true professional would develop the website, but with few conditions I'm evolving.

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

where it took me the longest to complete was to center the qr-code image with the container, but little by little I racked my brains and looked at my notes until I discovered a method

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

Just to know if the algorithm is right and where I could improve.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mustafa Sen•1,510
    @mustafasen97
    Posted 23 days ago

    Instead of using too much margin, put elements like images and text in the correct order in a container. When you give this container padding, it will have a more balanced and clean space in the corners.

    You can use it by researching the display flex, gap property to adjust the space between elements. Or it can be margin-top or bottom instead.

    Also, instead of using too many IDs, prefer using classes. In this design, you don’t need to give width to the image. Make it 100% width.

    The image will already appear centered thanks to its padding in the parent container. After all the above adjustments are made, write these for the image background-position: center;

    background-size: cover;

    Marked as helpful
  • Beauyonradee•40
    @Beauyonradee
    Posted 24 days ago

    clean code and easy to read

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