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

QR code component

Oscar Bocanegra•235
@obocanegra-dev
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


📝🎉 Hey there, Frontend Mentor community! I'm thrilled to submit my first solution and would love to receive your feedback on it. 😊

👋 Introduction: I'm excited to be a part of this amazing community and have recently completed my very first frontend challenge. It was a fantastic learning opportunity, and I'm eager to hear your thoughts on my solution.

🌟 Challenge: The challenge I tackled was QR code component. It presented a unique set of requirements and allowed me to dive into HTML and CSS to bring the design to life.

📚 Tech Stack: For this project, I used the following technologies:

HTML CSS

🧐 Approach: I approached this challenge by carefully studying the provided design and breaking it down into smaller components. I then focused on implementing each part using HTML and CSS. I made sure to pay attention to details like proper indentation, semantic HTML tags, and reusable CSS classes to ensure a clean and maintainable codebase.

💡 Learnings: While working on this project, I gained valuable insights into HTML and CSS. Here are a few key learnings:

Structuring content using HTML tags effectively Applying CSS styles to achieve the desired visual design Ensuring responsiveness and compatibility across different screen sizes

🌈 Feedback Request: I would greatly appreciate any feedback or suggestions you might have regarding my solution. It could be related to code organization, naming conventions, or even ways to improve the overall design. Your feedback would be immensely valuable in helping me grow as a frontend developer.

🙏 Thank you in advance for taking the time to review my work! I'm open to any feedback and excited to continue my frontend development journey. I'm grateful to be part of such an incredible community. 😄✨

Best regards, Oscar

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Oscar Bocanegra's solution.

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.