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

QR-component

yemisrach•10
@yemisrach-assefa
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


give me feed back

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Aemro bekalu melaku•600
    @aemrobe
    Posted almost 3 years ago

    @yemiserrach-assefa well done, good work as your first challenge and I have given you some feedback. I hope it will be helpful.

    1, you have to uncomment the .attrubtion class write your name on the place which says "your name here" because it helps to know who is the author.

    2, after u uncomment .attrubution class in your html file. you should use flex-direction of column inside your body element to make .attrubtion class below the .container element

    3, you should remove the width of 100% in the body element because it is 100% of the size of your screen by default.

    4, you should remove paddign left from you img element

    5, you shouldn't repeat the propertie which you already wrote again inside your media querie.the properties which you should write inside your media queries should be the properties which are different from the one which you wrote first. so I comment the properties which are repeated inside your code.

    6, you should remove the align-items propertie inside your img element because the align-items propertie only written inside the parent flex container or on the element which you write the "display: flex;" property.

    7,you should import the font family and use it in the body element which is given in the style-guide.md file.

    8, you should remove the text transform property which is used in the .white class.

    9, you should remove the <br> property and use margin property inside the h1 element.

    10, you should remove the width property, margin property from the img element because it won't make the image responsive instead use the margin property inside it's parent qr element and use the max-width of 100% inside the img element.

    11, you should use the font-size of the 15px inside the body element because all the elements inside the body element will use it so the h1 element won't look bigger.

    12.you should use the max-width inside the .container element to avoid bigger sizes of the .container element.

    13, you should increase the width of .container element inside the media querie to make it look good at ,mobile devices.

    14, use the background color of light gray inside the body element

    15, use the color of Grayish blue inside your paragraph element.

    16, you can decrease the font-size of the h1 element to make a look the same as given inside the design folder.

    17, it is recommended to use px value for border-radius property.

    18, you can increase the padding left and padding right for your paragraph element inside your the media queriy.

    Marked as helpful
  • M Irfan Ashraf•60
    @IrfanAshraf-pro
    Posted almost 3 years ago

    Hi @yemisrach-assefa, Great work done building the card, The image has no border on the left hand side. The paragraph is really hard to read and the colors scheme is a little off too. Believe this will help improve the card.

    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