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

Created a webpage for QR code using HTML and CSS

ganispydev•10
@ganispydev
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?

What I’m most proud of: I’m proud that I was able to create a clean and functional webpage using just HTML and CSS, without relying on frameworks or complex tools. It was satisfying to see the QR code displayed exactly as intended, and it gave me confidence in my foundational web development skills.

What I’d do differently next time: Next time, I’d like to make the page more dynamic by adding JavaScript so users can input their own text or links to generate a custom QR code. I’d also spend more time on improving the responsiveness and accessibility of the page to make sure it works better across all devices and for all users.

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

One of the main challenges I faced was positioning the QR code exactly where I wanted it on the page using only HTML and CSS. Without using layout tools like Flexbox or Grid, I relied on position: relative and position: absolute to place elements precisely. I used properties like top, left, and right to fine-tune the placement and ensure the QR code appeared in the desired location.

Another challenge was making sure the layout remained clean and consistent across devices. I overcame this by adjusting the positioning values through trial and error and previewing the page on different screen sizes to maintain a balanced design.

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

I’d like help with making the webpage more responsive across different screen sizes using better positioning techniques. Since I used relative and absolute positioning, it works well on certain devices but may not scale properly on all screen sizes.

I’m also interested in learning how to add JavaScript to make the QR code dynamic—allowing users to enter a link or text and generate a QR code instantly. Additionally, any suggestions on improving accessibility (such as for screen readers) or optimizing the page for faster loading would be appreciated.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on ganispydev's solution.

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.