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

Creating that QR code with Javascript.

Julian-Carlosama•10
@Julian-Carlosama
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have two questions! I would know the best practices for this project. I know it's basic, but I want to give me your feedback.

Thank you for your time and consideration.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David Gichuru•360
    @dxiDavid
    Posted over 2 years ago

    Hello @Julian-Carlosama 👋🏾

    Congrats on completing the challenge 🎉

    I have a few suggestions on how you can improve your code:

    1. HTML📃

    • Make sure your content is wrapped inside a <main> landmark tag. If you want to learn more about semantic HTML tags you can find that here.
    • Make sure that your images have alt text for screen readers which will improve accessibility for your future websites. Try to have descriptive text so that the person knows exactly what the image is.

    2. CSS📄

    • Avoid setting fixed values for dimensions like width and height. Instead set a max-width and max-height for your elements
    • Avoid using absolute units like px for anything other than border-radius or box-shadow. Use responsive units like em and rem which will make your projects more responsive.
    • To center your card you can try the following methods
    1. Using grid
    body{
         min-height: 100vh;
         display: grid;
         place-items: center;
    }
    
    1. Using flexbox
    body{
         min-height: 100vh;
         display: flex;
         flex-direction: column; 
         justify-content: center;
         align-items: center;
    }
    

    Another useful tip is to build a habit of setting custom properties for the styles found in the style guide and any other styles you might re-use.

    You might also want to set up utility classes for centering things to avoid repeating yourself throughout the code.

    Your solution looks great

    I hope you found this helpful 😁

    Happy Coding 🥂

    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 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