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

mobile first solution using HTML5 and CSS properties

pure-css
Aiswariya S•40
@Aiswariya3a
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?

The component is fully responsive and looks great on both mobile and desktop devices. Ensuring a seamless user experience across different screen sizes was a key goal, and I believe I achieved that effectively. I focused on writing clean, semantic HTML and well-organized CSS. Implementing Flexbox for layout made the alignment and spacing of elements consistent. This was particularly useful for centering the content both vertically and horizontally. For my other projects, I would explore using CSS Grid alongside Flexbox.

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

Maintaining consistent spacing and alignment between elements within the card, especially as the viewport size changed, was challenging. I used CSS custom properties (variables) to define consistent spacing values throughout the project. This allowed me to easily adjust padding and margin values and ensure uniformity. Flexbox also helped maintain consistent spacing by distributing space evenly among the elements.

What specific areas of your project would you like help with?

I used pure CSS for styling this project, but I'm curious about the benefits of using CSS frameworks like Bootstrap or Tailwind CSS. How could incorporating a framework have improved the development process or the final design? Are there specific scenarios where one framework would be more advantageous than another for a project like this?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • RSGames2019•60
    @RSGames2019
    Posted about 1 year ago

    Estou no inicio como você, então não sei o dizer sobre suas duvidas, mas sei que juntos podemos superar todos os nossos desafios.

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

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