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

QR code component solution | HTML, CSS, Flexbox

Vozmo•60
@V0zmo
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?

Doing the layout with Flexbox. For me, the hardest part of learning HTML and CSS is how Flexbox works, and how to contain HTML elements that is useful. Maybe with the next project, I should learn how to better contain elements and use Flexbox correctly.

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

Not knowing the CSS element to use, the responsive layout with Flexbox, and the @media queries for mobile view are quite challenging. How I solve this is; for the CSS element I can search through the W3School website, layout can be done with in-depth learning through articles, website, or even video, the media queries is knowing what element needs to be changed.

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

The layout responsive, especially with @media queries, any classes that contain 'display: flex' and the div classes element. What is the optimal way to do it and how to approach it differently optimize the code, clean the code, and also easy to understand.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Connor McLaughlin•120
    @Gingerlox
    Posted 11 months ago

    thank for your comment on mine!

    this looking great also, love the hover effect. one thing i would suggest is trying to avoid media queries if you don't need to. work mobile first, then add complexity for wider screens. I used the width and max width attributes together on my container to avoid the component stretching :)

    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

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