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

QR Code Component

Judith Uchechukwu Ezenwosu•20
@Uceeyjudy
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I should have started practicing earlier. After a long tutorial hell for 2 year, I am unable to build a simple QR code as per standards. Please do not refer me to another tutorial, I just need to practice more. Feedbacks would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Asongafac•110
    @Asongafac
    Posted almost 2 years ago

    keep practicing, but bear in mind the basics are very strong in any form of coding. be sure to know how to send a major div at center of screen ( display flex, height 100vh, width 100vw, align item center, justify-content center ... all this properties to the body )

    i will deeply advice you check the code given above by @Ratified

    Marked as helpful
  • RatifiedGeorge•670
    @Ratified
    Posted almost 2 years ago

    Hello. It needs practice to be able to come up with these solutions. You'll eventually be able to come up with proper CSS. Let me provide you with my code to this solution, try it out and check if it helps you. QR Code Component. Lemme know if you have any questions. I'd be glad to help.

    Marked as helpful
  • DESALEGN MIHRET•250
    @desalegn12
    Posted almost 2 years ago

    from what you were saying, I appreciate that you can admit your flaw because that is one sign of growth. the most important thing you have to do is just practice CSS. we all are struggling to master CSS skills but CSS[grid, flexbox, position are enough], not anything else. if you can pseudo-elements. I hope you'll come back and say thank you! Good practice!

    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

Oops! 😬

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

Log in with GitHub