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

Responsive QR code card using CSS and bootstrap

bootstrap
Mariem Bchir•100
@Mabchir
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Continued development

It would be helpful to understand

  • The reason why some added values in CSS need "!important" to actually show up.

  • How to center any element in the screen regardless of the screen/browser/device used

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 3 years ago

    I recommend you don't use bootstrap or any other libraries while learning. This will actually hold back your progress.

    If you learn css, html and js yourself you'll be able to easily pick up any library you want later on and understand exactly what they're doing, why they're doing it and what the trade offs are in each library.

    Good luck

    Marked as helpful
  • Nakoya Wilson•1,530
    @nakoyawilson
    Posted over 3 years ago

    Adding to @denielden 's comment, in your index.html file you have inline css on line 26 (<div class="card" style="width: 18rem">). If you remove the style="width: 18rem" then you would not need the !important for the width: 320px; for the card in your style.css file.

    Marked as helpful
  • Travolgi 🍕•31,300
    @denielden
    Posted over 3 years ago

    Hi Mariem, great job! Congratulations on completing the challenge.

    • The reason why you sometimes have to use !important is because the css is read in cascade and the last classes overwrite the previous ones. It is a good idea to use as little as possible !important because it makes management of the CSS difficult.
    • The best way to center the element is to use flexbox

    It would be helpful to understand:

    • css_important
    • Cascade_and_inheritance

    Also i have a few suggestions for you:

    • add main tag and wrap the card for Accessibility
    • remove position: absolute; top and left properties from card class
    • use flexbox to the body for center the card. Read here -> flex guide
    • set heigth of body to 100vh because Flexbox aligns to the size of the parent container.

    Overall you did well :)

    Hope this help and happy coding!

    Marked as helpful
  • Hexer•3,620
    @EmmanuelHexer
    Posted over 3 years ago

    Great job overall man. Keep it up

    • To fix your accessibility issues wrap your card with main element.
    Marked as helpful
  • Ali•260
    @alihuseynzade23
    Posted over 3 years ago

    Hi @Mabchir.

    It is look like your qr component not well centered. Try to use position: absolute with top and left 50%. Do not forget about translate: rotate too.

    Good luck :)

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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

Oops! 😬

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

Log in with GitHub