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

QR Code - Solution

Eni•180
@EnidaShehu
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  1. What could I have done differently without using Bootstrap?
  2. What is something that needs to be changed about the code?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yash Joshi•450
    @yashgjoshi20
    Posted about 2 years ago
    1. You can set the container in the middle of the screen then whatever changes user makes can be added in properties of the styles.css later on to perfect it.
    2. You can add the .container { display: absolute; top:50%; left: 50%; transform: translate(-50%, -50%); } .
    Marked as helpful
  • Bader Idris•2,880
    @Bader-Idris
    Posted about 2 years ago

    You can set the container in the middle of the screen whatever user changes it when you add these properties to it in CSS: .container { display: absolute; top:50%; left: 50%; transform: translate(-50%, -50%); } the new feature is transform, it has many lovely properties you can discover, I personally love it

    Marked as helpful
  • Yemi•40
    @layerdbag
    Posted about 2 years ago

    You actually do not need bootstrap for this challenge as it is a single component that can be done using CSS. You could center your component by using:

    html, body { 
     min-width: 100%;
     min-height: 100%;
     display: flex; 
     justify-content: center; 
     flex-direction column;
    }
    

    You could also add a box-shadow on the card component to make it look like the design.

    .card { box-shadow: 0px 5px 7px var(--color); } /* where --color is your chosen color*/

  • Yemi•40
    @layerdbag
    Posted about 2 years ago

    Your solution does not include semantic HTML. For example, you could wrap your component in an article element which will be placed in a main element to make it more semantically acceptable.

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

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