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

html and css

M'I'E•10
@MIE-CODE
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The project was built base on basic html and css code , with that alone you can build it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kimo Spark•2,190
    @kimodev1990
    Posted over 1 year ago
    • To center your DIV container in the middle of your website:
    body {
    display: flex;
    justify-content: center;
    align-items: center;
    min-height: 100vh;
    }
    
    • It's better in the future not to assign definite values such as in class .text-container width: 250px & in class .qr_code width: 250px --- height:250px, It's better to give them percentage values in relative to size of container for better responsive design.

    • Adding up with previous point, If you need to assign a value to an element , you could check on and use clamp ( ) method in your coding for font-size, width, etc., So your designed sizes will change according to the viewport dimensions having a responsive design and will be suitable for any device layout.

    • you'd like to wrap the image inside DIV for better design & code control.

    Hope you find this Useful & Helpful.

    Other than that, Really Nice work & keep Going on.

    Marked as helpful
  • Hussein Samy•340
    @HusseinSamy
    Posted over 1 year ago

    Greetings @M'I'E, 👋🏻

    Fantastic progress on embarking on the journey toward your dream!

    I'm thrilled to see your engagement with this platform to enhance your design skills. However, I have a brief recommendation regarding your commit messages. Consider adopting some conventions such as this; it will prove beneficial in your future career, especially when collaborating with teams.

    Hope you find this valuable! 😇

    Keep up the outstanding work, and enjoy your coding journey! 🚀

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub