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

Qr Code Component

Brian Muniz Silveira•200
@BrianMunizSilveira
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?

As I mentioned earlier, using variables with CSS is a great practice in my opinion. Even in a small project like this, it already helps a lot in development. Next time, I would make better use of class.

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

I had difficulty with alignments, both for texts and boxes. I had to review past studies and consult my previous codes to overcome these challenges. Additionally, I received help from a friend who gave me a small push in development.

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

I would like help with alignment because I still feel a certain difficulty in getting the alignments right. However, I believe that with a little more practice, this will become easier. I still feel lost with display: flex and its properties, but I will be practicing. I believe this was my biggest challenge; the rest was a smooth process.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan de Bruijn•3,220
    @DylandeBruijn
    Posted 12 months ago

    Hi @BrianMunizSilveira,

    Great job on your completing your project it looks very close to the design specifications. I like that you took the time to write a detailed retrospective.

    A bit of friendly constructive feedback:

    • Try putting a bit of padding on the left and right of your body. Or wrap your card in a separate container that applies this spacing. This is recommended so your card has some spacing between the sides of the browser on smaller viewports.

    • Nice use of a reset stylesheet. I would give your main CSS file a more descriptive name however, like main.css, style.css or styles.css. Other developers will then have an easier time knowing where the styles come from.

    • I suggest using min-height: 100vh instead of height: 100vh on the body element. If your content ever grows and it exceeds the height of 100vh you'll run into overflow issues.

    • I suggest using a p tag for your description instead of a span. This is a little bit more semantic. A span is generally used to style a specific piece of text inside a p or h1 for example.

    If you have any questions about flex specifically I would be happy to answer them.

    I hope you find my feedback helpful!

    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