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

QR code component using Flexbox

Allen Padilla•10
@allenJcodes
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How can I improve my work? Please leave some comments.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    Hello Allen, congratulations for your solution!

    Answering your question:

    You can improve you code using semantics tags to replace the divs, for example using <main> to replace the div, reduce your code eliminating the unnecessary divs this challenge requires only one div to hold all content (h1, p and Img). To save time you can use variables to work with the colors. Remember to replace the h3 with h1, and to follow a hierarchy sequence for headings using the sequence h1, h2...

    Hope this helps, happy coding!

  • Stacey•30
    @staceysav
    Posted almost 3 years ago

    Hi Allen! The page with the QR-code looks excellent! The code is readable and short, it is quite easy to understand what's going on there. I also liked that you used variables. I have no experience in coding, so I can't give you useful feedback. I can share a comment that I got myself: you could wrap the card with the <main> tag to improve navigation for users and engines. This will indicate that the card is the main content of the page. Keep posting your solutions :)

  • Illyaas•700
    @Illyaas4Show
    Posted almost 3 years ago

    Hi, welcome to the community

    This is an amazing solution you've got here. It is almost identical to the design, well done! All you need to do is reduce the width of the card and it will be awesome!

    Hope this helps, Happy coding!

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

Oops! 😬

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

Log in with GitHub