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

QR-Card using Media queries

pooja-bharadwaj•40
@pooja-bharadwaj
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?

What I'm Most Proud Of: I’m proud of successfully completing my first responsive web design project and deploying it live using GitHub Pages. It felt great to see the design come to life, especially after figuring out how to center elements and make the card look visually appealing on both mobile and desktop devices. I also enjoyed learning the workflow of using GitHub for version control and deployment, which was completely new to me.

What I Would Do Differently Next Time: Next time, I would:

  1. Organize my project files better by using a dedicated folder for images and assets right from the beginning.
  2. Write a README file with clear details about the project to make it more professional.
  3. Optimize the image for faster loading on the live site.
  4. Test the site more thoroughly to ensure all elements work as expected after deployment.
  5. Use a CSS preprocessor or modular approach to manage styles more effectively as the project grows.
What challenges did you encounter, and how did you overcome them?

Challenges:

  1. Image Not Displaying on the Deployed Site: Initially, the QR code image wasn’t showing on my live website, even though it worked perfectly in my local preview. I realized it was due to incorrect file paths, but fixing them while keeping the project organized was confusing for me.

  2. GitHub Workflow: As a beginner, I struggled with understanding how to manage commits, repositories, and file organization during deployment. At one point, I deleted the repository and had to restore it, which added more complexity.

  3. File Organization: When trying to move the image file into a separate folder (e.g., images/), the website stopped working because I hadn’t updated the path correctly in my HTML file.

How I Overcame Them:

  1. I referred to GitHub documentation and followed step-by-step tutorials to learn about deployment using GitHub Pages. Restoring the deleted repository taught me a lot about handling such situations.
  2. To resolve the image issue, I placed the image in the same folder as index.html for simplicity during deployment, ensuring it worked. In the future, I’ll pay more attention to organizing my files from the start.
What specific areas of your project would you like help with?

Improving File Organization for Deployment:

  1. I’d like guidance on how to properly structure my project files (e.g., keeping images in a folder) while ensuring everything works smoothly during deployment.

  2. Understanding GitHub Pages Deployment: Although I managed to deploy my project, I’m still unsure about some steps in the workflow, like handling uncommitted changes and ensuring all necessary files are included.

  3. Optimizing HTML and CSS Code: I’d appreciate feedback on whether my HTML and CSS are structured efficiently and follow best practices, especially for responsive design.

  4. Debugging Issues with Missing Resources: Help with understanding why resources like images sometimes fail to load after deployment and how to prevent this issue in the future.

  5. Exploring Advanced Styling Techniques: Suggestions for enhancing the design and learning advanced CSS techniques to make the project more visually appealing.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Busari Akeem Tunde•370
    @Aalphakeem-Adroit
    Posted 6 months ago

    I've gone through your code. You've done well. Keep it up 👌✨🎊

    Add .card {border-radius: 20px; padding: 15px;} to your card and see the difference.

  • Rupak Mukherjee•1,370
    @hannibal1631
    Posted 6 months ago

    Well Pooja first of all congrats on completing your first project here. Now i read your whole story that you put here and i would like to tell you we all faced similar problems when we started.

    Now as per keeping your files, you don't have to move anything anywhere because the main folder that you download is already well structured(as you'll notice later on). The only files you need to create are html, css and js(for js projects).

    As of the readme file, it's already there so you don't have to create one, but you can if you want to.

    You faced the image bug because you tried to place the image elsewhere. just give it a correct directory and you won't face this problem.

    If you want to learn about github and how to use github properly, we can connect via discord and i can explain everything. So let me know if you would like to connect.

    Overall you did a great job. The styling could be better, and you should always make a separate css file to write styles, it's not a good practice to put them inside html.

    Happy Coding!!!

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