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

HTML and CSS

Jacob Prince•30
@jacobchandy
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pranjali Sargar•520
    @Psargar616
    Posted over 1 year ago

    Hey @jacobchandy! Impressive Work on the QR code component Challenge! 🌟

    I hope you're doing fantastic! I just had the chance to check out your solution challenge, and I have to say, I'm really impressed! Your work on this project is absolutely outstanding! 👍

    Here's what I loved:

    Stylish Design: Your design is sleek and eye-catching. The color palette and typography choices are spot-on, making it visually appealing.

    I want to suggest just a few changes to get that pixel perfect design:

    .component {
       //add padding and increase border-radius
        border-radius: 20px;
        width: 320px;
        box-shadow: 0 0 10px rgba(0, 0, 0, 0.2);
        padding: 10px;
    
    }
    .image img {
        margin: 10px;
       //remove 2 lines below
        /* margin-bottom: 0px; */
        /* padding-bottom: 0px; */
        width: 300px;
        border-radius: 15px;
    }
    
    also for h2 you can use color from style guide
    
    

    Responsive Layout: I noticed your solution adapts flawlessly to various screen sizes, which is a crucial skill in web development.

    Code Quality: Your code is well-structured and easy to follow, reflecting your strong development skills.

    You're doing fantastic, and these suggestions are just meant to help you polish your skills even more. Wishing you all the best in your coding adventures! Looking forward to seeing more of your brilliant projects! If you found this feedback useful, please mark this comment as helpful

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