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

QR-Code Introductory Challenge

P
Brian Meinert•370
@bmeinert8
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?

This was a fun little challenge to take on in the beginning stages of learning web development. Overall, I found joy in every aspect of the project, but what, I believe, brought me the most joy in the project was seeing the finished product. There's nothing more satisfying than seeing your finished work look and work just as you intend it to.

If I could do anything differently next time, I would go about the project in a different manner. This time through, the process I took was writing out all of the HTML, then writing out all of the CSS. Instead, I would create a portion of the HTML, ie. a div, then give that element its class and style, before moving onto the next section. I just feel i have a better understanding of what I'm doing and building going about it in small sections at a time that way, than the route I took this time.

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

The biggest challenge I faced in this project was getting the main div that held the QR image and text centered on the page. I tried a few different methods and eventually settled on flexbox to get everything centered, thank you google for the refresher.

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

The part that I would like the most help with is writing cleaner, more readable code. Getting into development I want to be able to write code that is very clean, readable, and functional. Any advice and insight on this would be greatly appreciated and accepted!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Safynaz Abdelraheem•90
    @safyabdelrahem
    Posted 9 months ago

    This is incredible.

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