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

QR code component

react, bootstrap
Elisabeth Erkekoglou•180
@elic4vet
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone, Here is Elisabeth, I just created the solution for this very first app. It's not sure if it's 100% perfect - I am still learning 😅 Please feel free to share any suggestions or comments you may have 😄 Kind regards, Elisabeth

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ranti ogunrinde•210
    @Ranty09
    Posted almost 2 years ago

    Great job, Elisabeth! I noticed that you skipped the edges of the image, just a small suggestion. Why not add some border radius to the image edges, just like you did for the main card? Overall, though, I must say this design is looking fantastic, keep up the amazing work.

    Marked as helpful
  • P
    Atif Iqbal•3,320
    @atif-dev
    Posted almost 2 years ago

    Hi, congrats on completing the challenge. Better take care about following points:

    • For centering the card do as:
    body {
    min-height: 100vh;
    display: grid;
    place-content: center;
    }
    
    • Use semantic tags to fix accessibility issues.
    • It is preferred to use responsive units(rem for font size and em for margin and padding)
    • When we open GitHub repository link, at right side you will find an About Section. There, also include a live preview link of your project. It is better for someone to check your live project while interacting with code.
    • Write your own README file in your GitHub project's solution and write about your working flow, findings, newly learned things, useful resources, etc.

    Hope you will find this Feedback Helpful.

    Marked as helpful
  • Avocodev•270
    @avocodev
    Posted almost 2 years ago

    Hello greetings 🖐🏻.

    Great job for your challanges, but i want to corrected some ur desain.

    First, at the your card use very radius big, maybe u can add 10px or 5px for the better then.

    Second, at the shadows for make a better shadow you can follow my tips, example: box-shadow: 0 0 20px rgba(0, 0, 0, 0.1);

    First zero it's mean position for a shadow to right (positive value) and left (negative value), example like if you add 10px for the first zero, mean you add a position of shadow to right some 10px.

    Second zero same like first zero, but for the second zero make move to top (negative value) and bottom (positive value), how to use same like first zero.

    Third '20px' it's mean for size the shadow

    and the last one is rgba for the color, triple zero for color and the last value is alpha or opaciry from the color.

    Third, maybe u can use width with % value for make a responsive, like width: 80% and for height u can set everything u want. dont forget too add some border radius like example in desain.

    Fourh, author you dont make some author just change the default style.

    Thanks, I hope this make help you for the better coders 👍🏻

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

Oops! 😬

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

Log in with GitHub