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

QR code component

web-components
DanishZubair•20
@DanishZubair
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have done this challenge by following a tutorial. I want to ask how can I stop following tutorials and build projects, as I have knowledge of HTML and CSS, I have done many courses and I understand most of the advanced concepts in HTML and CSS, but I am not able to build the project. Can you suggest me what to do, as I am really worried about this. I have 2 years of experience in HTML and CSS. Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kushal Rai•30
    @kushal-rai
    Posted almost 2 years ago

    Hey mate! I'm actually on the same page as you are, what I'm doing is trying to do as much as I can by myself and I don't go about finding the solution straightforward forward but what I do is, where ever I'm stuck I try to find a way out using web or chatGPT but trying to use those resources as less as I can, remember you can't memorize everything, nobody dose!

  • C4rlos•410
    @solracss
    Posted almost 2 years ago

    "how can I stop following tutorials and build projects"

    You've just answered yourself. Just stop code along and start using your knowledge by doing very easy projects like this one.

  • tomdu3•20
    @tomdu3
    Posted almost 2 years ago

    a nice one. Now, what I would propose you to do is to start working on some projects for yourself. Maybe you could start by building one small HTML/CSS project alone. Make one page only site with some details: navbar, header, hero image, headings, sections, articles and images, one unordered list, small contact form and a footer. I would suggest to you this article for the directory organization: https://www.codecademy.com/article/f1-u2-create-first-prj. and this tutorial to understand the responsive design: https://courses.kevinpowell.co/conquering-responsive-layouts By doing your own projects you can learn a lot and always ask some to look at your page and give you some feedback on discord/slack,...

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

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