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

QR Code Challenge + custom shadow in HTML & CSS

Prinz•60
@maxnoelp
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?

Most prud of my shadow and that i finished the Challenge. I learn coding since two weeks and i love it.

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

For me its very tricky to use the Flexbox. But i finished it, with some that i leraned.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ehsan•210
    @Ehsan-eslami
    Posted about 1 year ago

    Hi @maxnoelp. You've done a great and a cool job, be proud of yourself. Just a few small tips that could look awesome, add font family "Outfit" to your project and fade the shadow more. The rest is good.

    🥳happy coding.

  • noreenfatima775•70
    @noreenfatima775
    Posted about 1 year ago

    Hi @maxnoelp,

    Great job on your web project! To enhance it further, consider making the website responsive so it looks good on all devices. Also, adding subtle box shadows can improve the visual appeal. Switching to the 'Outfit' font family will give the site a cleaner look. Finally, including a detailed README file will help others understand and contribute to your project more efficiently.

  • Umesh Suwal•180
    @umeshsuwal
    Posted about 1 year ago

    Use the font-family: 'Outfit', sans-serif; and remove the box shadow for the container..

  • Prinz•60
    @maxnoelp
    Posted about 1 year ago

    why is the Screenshot so diffrent to the website?

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, SASS, 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

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