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

QR Code

Kate•60
@devknightingale
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?

Proud of: I thought going in that trying to build a page without following a tutorial would take a lot longer than it did.

What I would do differently: With a bit more experience, I would like more knowledge of building for mobile screens. I tried to fiddle with the css a bit and test how the page would look by collapsing the browser window, but I don't think that's how people test mobile sites. I would like more knowledge on how to do that next time.

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

Not enough containers... I had trouble centering it vertically before realizing I needed to wrap the whole thing in another element to allow vertical centering. From what I googled there are other ways but flexbox seemed simplest.

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

I'd like to figure out how to use the MobileView extension in VSCode. I installed the extension but when I start it up, it doesn't seem to actually have a live preview of the site I'm building. I didn't have a lot of time to fiddle with it before work though so I let it go for the time being.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eirik Andresen•60
    @ehandresen
    Posted about 1 year ago

    While you did attempt to test the page by resizing the browser window, there are more effective ways to ensure your design is mobile-friendly. Consider using tools like Chrome DevTools for responsive design mode or dedicated mobile testing tools to get a more accurate representation of how your site looks on different devices. Addressing the issues with the MobileView extension in VSCode is crucial. Ensure that your development tools are set up correctly to save time and avoid frustration. Look into alternative extensions or plugins that might offer more reliable live previews.

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

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