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

qr code attempt

Suki•90
@Suksman03
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedbacks are welcome please.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dennis A. Boanini•210
    @DennisBoanini
    Posted almost 3 years ago

    Hi, try to resolve your HTML errors. First error tell you that the alt attribute is missing on img tag and this is useful when image is not loaded and in this case the alt text is showed. The other error tell you that you placed the style tag in wrong place.

    For the card may you can try to increase the sizes

    Marked as helpful
  • Kent O'Sullivan•1,870
    @12Kentos
    Posted almost 3 years ago

    Hey @Suksman03,

    Nice job on completing the project it looks great!

    I looked through your css file and noticed you selected elements directly several times like so.

    p { margin-top: 15px; font-size: 15px; font-weight: 700; font-family: 'Outfit',sans-serif; text-align: center; color:hsl(218, 4 4%, 22%); }

    While this isn't a problem for small projects like this, it's best to get into a good habit now of selecting pretty much everything with classes, or id's or at least with a little more specificity. That way when you are making changes to a p element, it won't change every single p element on your page. This will help you avoid a LOT of headache on bigger projects.

    Keep up the great work!

    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

Oops! 😬

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

Log in with GitHub