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

QR code component challenge plain HTML & CSS

AmyH-goose•120
@AmyH-goose
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?

I was most proud of being able to get the project done. This is my first time not being hand-held through a project or in a class room environment. However, I struggled a lot in knowing where to start and how to execute what I needed to do. Hopefully, next time I can break the task down into smaller steps and be less overwhelmed.

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

It was hard for me to know where to start tackling the project. I decided to figure out the tags needed before I did the styling. When I got to the CSS part, I tried to refer to the figma design files.

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

I would like to know how I can make the project more responsive and how the process of coding should look like? For example, what kind of general checklist should I go through in my head when approaching a project. As for responsiveness, what kind of properties or tags in css or html should I use and when do I know when to use them?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Burak Uğraş•90
    @burakugras
    Posted 7 months ago

    Hello,

    Your design and codes looks amazing. It written correctly. However I would expect you gave margin attribute for body. So, thanks to this way you could have centered your card vertically.

    Happy coding!!

    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

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