Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

QR Code Display Page

Srivatsan•150
@srivatsan-droid
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Since its my first Project Learnt how to create a website according to the requirement given and also styling is difficult part which took most of my time so my plan is to improvise in styling next time

What challenges did you encounter, and how did you overcome them?

First challenge is i was not able to get the box under which the image and the rest of the text goes into so used field set at first and then by styling itself i tried to come up with the solution Next Thing is alignment according to the design provided was tough so in this case tried adding padding at first with different outcome of number but then used margin property and justify content in css

What specific areas of your project would you like help with?

i need help in the design part where i need to understand how can reduce the size of the box and come up with the exact match of the design and also how to add border at which place any clue to identify so it can be useful for me next time when i am trying something new

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Akash Mishra•160
    @akashmishrahaha
    Posted about 1 year ago

    Take your time mate! You got it.

    Marked as helpful
  • Uche Ofatu•350
    @Macnelson9
    Posted about 1 year ago

    Hey there! Congratulations on your completion of this challenge! I see your QR code image isn't displaying, I myself encountered this same issue too. What you need to do is to change the file path inside of your html that you are hosting the page from.

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