Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Static QR Code built with just HTML and CSS.

Todd Moussallem•110
@rtoddm
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 is a simple project but it my first non-tutorial project since learning to code so I am proud of simply being able to complete it on my own.

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

The main difficulties that I encountered were learning to get the appropriate information from the Figma file and getting the page to display properly on GitHub Pages (it was a file path issue).

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

Have I completed this challenge as intended? The design file in figma does not show any additional background but the "preview" file shows an additional background applied behind the grey box background.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Johann Maldonado•100
    @Johann-Alpha
    Posted about 1 year ago

    Click on the link I sent and it'll give you an idea of what you have to do. Do not worry about them saying there are mobile or desktop versions. When you do the desktop version, mobiles will accommodate the content automatically.

    Marked as helpful
  • P
    Johann Maldonado•100
    @Johann-Alpha
    Posted about 1 year ago

    Hi @rtoddm. I think that you misunderstood the aim of the challenge. You shouldn't have replicated the screenshot. On the other hand, you should have created the page for desktop, and it would automatically adjust for mobiles.

    My challenge isn't perfect and I have a lot of suggestions from our colleagues that I have to implement. I will share my URL so that you can see what it was all about. Click here for the QR code challenge

    Cheers,

    Johann.

    Marked as helpful
  • Todd Moussallem•110
    @rtoddm
    Posted about 1 year ago

    Hi @Johann-Alpha, thanks for the feedback! Perhaps I'm just a bit confused as to the directions for the challenge. The description says this is a good challenge if you haven't learned about building responsive websites yet. So I admittedly was unclear as to what that meant since there was a mobile and desktop view. Can you help clarify for me? Thanks for the help!

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

Oops! 😬

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

Log in with GitHub