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

QR code component solution using CSS

Yash Goswami•70
@Yash-devasp
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 complete my first challenge on frontendmentor.io and with this I am starting a new journey on this path. I had a lot of fun completing the first assignment.

As I am a beginner and have just started learning about web a couple of days back so I am sure my code can be improved. Please help me in my journey by pointing out ways in which my code can be improved or if there could be a better way to tackle a problem.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Naveen Gumaste•10,420
    @NaveenGumaste
    Posted over 3 years ago

    Hello Yash Goswami ! Congo 👏 on completing this challenge

    Let's look at some of your issues, shall we:

    • Why use <p class="head">Improve your front-end skills by building projects</p> you should use h1 here as it is title of the card

    • the background shadow is very dark so make it more soft

    • Read style-guide and add the font-style and size along with weight

    • Add equal padding or margin for the qr img and the texts

    happy Coding😀

  • Abhik•4,820
    @abhik-b
    Posted over 3 years ago

    👋 Hello Yash ,Congratulations on completing your 1st challenge. Your solution is fantastic & it is very responsive 🤩👌

    Some of my opinions I am sharing with you :

    • give margin: 0; to *{ } to remove unwanted margin from all elements
    • remove the height from card & give gap:1em to make the card look more like the design
    • your box-shadow is very nice

    Very Well Done 🤩 & Please keep coding such amazing solutions 🥳👍

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

Oops! 😬

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

Log in with GitHub