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

QR Code Component Card Built with HTML and CSS

Allyson S.•190
@allyson-s-code
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, thanks for looking. My question with this project is mainly about setting up the files and what is appropriate to include in the GitHub repo? For example I ended up adding all my files after downloading and now I have design files in there. Should I delete those to keep the repo cleaner? Or is it helpful to have them there? Also, for a small project like this is it appropriate to have a separate css file with a normalize file included? Thanks so much!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bradley Smith•230
    @bradleyhop
    Posted over 3 years ago

    Your project look great! I took a look at your github repo and it seems pretty easy to navigate. I included the design files in my solution mainly because this is a learning exercise, and I wanted to show what I was working from. You could throw the design markdown file in the design folder to keep all that info together.

    I've done only one other Frontend Mentor project, but I'm paying for pro, so I downloaded the Figma design file. Since we're not supposed to upload those, I just used the readme.md template they provide to describe the project, etc.

    Your normalize.css is empty, so it's safe to delete. I'm not familiar with the normalize.css package, but as far as github pages is concerned, there's no information in that file to process. I only had one CSS file in my solution with just setting the margin and padding to 0, and box-sizing: border-box to clear out browser defaults.

    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