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

QR Code Project using Visual Studio Code, Figma, and Chrome Dev Tools

James Atkins•70
@End-Us3r
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?

I'm just happy to get started on this platform. I am proud of finally using Figma for something, I don't use designing or wireframe tools as much as I should so hopefully, I'll get some good practice here.

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

It wasn't that challenging for me, I've been messing around with code, IDEs, and Git/GitHub for a while now so I'm used to the tools.

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

I use Chrome Dev Tools to try to design better webpages for RWD but sometimes the screen doesn't adjust for mobile phone screens, like it's lagging, and even when I refresh the page it still doesn't adjust the layout. Does anyone else run into this issue?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted 10 months ago

    Hi!

    Well, I can't be sure what exactly happened on your screen, but as I can see your card doesn't adjust to various screens cos you hardcoded width of the body tag. The initial width of this tag is equal to the screen size so it's better not to overwrite it.

    As for height of the body use min-height: 100vh. This way it'll take all screen's height and could stretch if the content will be larger.

    And another couple suggestions:

    • It's better to use rem values for font sizes. It's a special values which depends of the browser font settings and provide better user experience and responsiveness.
    • Every page should contains main tag.
    • You can skip the div wrapper for the image and style it directly.

    Hope it could helps =)

    Congrats with your first challenge here, good luck =)

    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