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

css: webfonts, box. HTML: include picture

Adabe4•60
@Adabe4
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

  • beowulf1958•1,850
    @beowulf1958
    Posted 11 months ago

    Congratulations on completing this challenge. Your card looks really great, just like the design. I do have some suggestions.

    First, your styles are all over the place: in-line, internal, and external. In order to maintain the site more easily ( and make it scalable) you should have all your styles in one place, preferably in the external file. In-line styles are a no-no; they make fixing problems much harder. So move the .attribute styles in the <head> to "qr-code-component.css", as well as the img styles.

    img {
            width: 100%;
             border-radius: 5%;
    }
    

    Second, your next step is to find a way to center the card on the screen. One way is to use flexbox, another way is to use grid. If you look at how other people solved this challenge, you will see what I mead.

    Hope this helps. Keep on coding!

    Marked as helpful
  • Mahrukh Adeel•10
    @Mahrukh-Adeel
    Posted 11 months ago

    Your solution looks good! However, centering the card on the screen would make it more similar to the original design. Also, changing the heading font to the darker blue mentioned in the starter pack would be great.

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