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

Designed qrcode challenge using html and css.

bootstrap
Rakshith J•240
@rakshithjodukallu
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is the simple qrcode task that completed in 30mins. add the text column wise and make the div block center. Give me Your valuable comments, Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hi @rakshithjodukallu, congratulations on your first solution!👋 Welcome to the Frontend Mentor Coding Community!

    Great solution and a great start! From what I saw you’re on the right track. I’ve few suggestions for you that you can consider adding to your code:

    Remove the margin-top and align the whole content using just the body.See the code below:

    body {
        min-height: 100vh;
        background-color: #d5e1ef;
        margin-top: 200px;
        display: flex;
        align-items: center;
        justify-content: center;
        flex-direction: column;
    }
    

    ✌️ I hope this helps you and happy coding!

    Marked as helpful
  • Nelson Nzewi•270
    @nzewi
    Posted almost 3 years ago

    Great solution there Rakshith J

    1.<img src="./images/image-qr-code.png" class="img-fluid" alt=""> You can add a value to the alt tag because the image is not merely decorative but conveys something meaningful.

    2.<div class="codeouter"> It would be good if you used more descriptive class names to help other developers understand your code better and also help you in the future to understand.

    3.Use <main> instead of a simple <div> . This way, you improve the semantics and accessibility of your site, showing which is the main block of content on this page. Every page should have a <main> block

    4.The main heading has the tag <h4>. You should replace it with <h1> since this heading is the main title on this page. Every page should have one <h1> to declare the most important title and you should follow the hierarchy using the heading sequence (h1, h2, h3, h4, h5) and never jump a level.

    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