Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Qr using basic CSS and HTML

P
Ricarddo96•100
@Ricarddo96
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

  • Car•270
    @Lukas3162000
    Posted 9 months ago

    Hey Ricarddo96, Unfortunatly im a total beginner myself, so i can only feedback you on the size of the h1 which looks a bit too small and the left and right paddings on the content-part of your card.

    The Shadow looks a bit too dark aswell, but these are only small css tweeks. I really like that your card is responsive and the border-radius goes from rounded to sharp the smaller the card gets - great work ! :)

    hope that helped a bit atleast :D

    kind regards, Lukas

    Marked as helpful
  • P
    Tom Winskell•180
    @tomwinskell
    Posted 9 months ago

    Here's some suggestions that I though might help.

    • One of the biggest issues I can see if the alignment of your component. It should be centred on the screen. It's worth learning how your can create layouts using flexbox. Flexbox makes it really easy to center something on the screen. Check out https://css-tricks.com/snippets/css/a-guide-to-flexbox/.
    • Nice reset with the use of * in your css. There are also pre-prepared CSS resets which you can use https://meyerweb.com/eric/tools/css/reset/.
    • Organizing your CSS into sections with comments as headers can help. This project is small but as your CSS files getter bigger and longer, sections and comments can really help. I find it has been useful to practise this with smaller projects first. For example:
    // Font-styles
    h1{
        font-size: 21px;
    }
    
    p{
        font-size: 15px;
        color: hsl(216, 15%, 48%);
    }
    

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