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

QR Code Component by Watership | Desktop First

vue
Watership 🌊•320
@Watership6
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey, I am Watership💧🙋‍♂️. And this is my solution for theqr code component challenge. 🚀

Goals Accomplished ✅:

  1. I was able to get better with VueJS and Vanillia CSS🛩️
  2. I got better with ⭐The Basics⭐

Built With🪄:VueJS✔️Vanilla CSS✔️

Overall, I really liked this challenge, and would appreciate any feedback that's given. ❤️

Watership💧🌊✌️🙋‍♂️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Boots 😺•1,610
    @adityaphasu
    Posted almost 2 years ago

    Hello, @Hyoaku!

    Nice solution! Just some fixes regarding CSS:

    • Try using a CSS reset in your projects like this one to remove all the default styles that the browser applies.
    • Currently due to no CSS reset the browser adds a little bit of margin to the body and hence you can see that there's this scrollbar on the page.
    • Use min-height:100vh on the body instead of height:100vh because using height:100vh would cause the content to overflow and might not be fully visible. On the other hand, min-height: 100vh ensures that card will always be at least the height of the viewport, but it can expand if the content inside requires more space this prevents content from being cut off or inaccessible.
    • Instead of giving the p tags width you can just give the <main> tag width: 17rem and remove the width: fit-content from it.
    • I see you have used rem units in most of the properties but not font sizes so try to use rem to set font sizes as well so that they scale well if it's a scalable layout. (this card doesn't scale but its good practice to use rem for font sizes)

    Apart from these few things good job on the challenge with Vue.js! 🙌🏻 (I also want to try Vue someday haha)

    Keep up the hard work and 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
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