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

Responsive Landing page using HTML, CSS

MrUnik•30
@FutureCiso
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted 6 months ago

    Hi @FutureCiso, 👋

    I reviewed your code and noticed a lot of great improvements! You've made good strides with your design, and with a few tweaks, it can be even better. Here's my detailed feedback and suggestions:


    1. Centering the Card Design

    To simplify and enhance the centering of your card, use the following CSS snippet:

    html, body {
        display: grid;
        width: 100vw;
        place-content: center;
        height: 100vh;
        background-color: var(--bg-color);
    }
    

    This approach is cleaner and avoids unnecessary complexity. 🌟


    2. Avoid Fixed Width/Height

    In your .main-page and .container styles, avoid using fixed dimensions like width and height. Instead, let the child elements dictate the size for better responsiveness. Replace the commented-out properties with these improvements:

    .main-page {
        background-color: var(--bg-color);
    }
    
    .container {
        max-width: 320px;
        background-color: var(--container-color);
        border-radius: 15px;
        padding: 1rem;
    }
    

    Benefits:

    • Increased design flexibility.
    • No need for media queries to handle responsiveness. 🎯

    3. Use Consistent Units

    Replace percentages (%) or viewport dimensions (vw, vh) with rem or em for better scalability and maintainability. Also, use max-width instead of width to reduce code overhead and improve adaptability.


    4. Remove Redundant Media Queries

    The media query code between lines 69-94 can be safely removed as the suggested max-width approach eliminates the need for them. Less code = easier maintenance! ✂️


    5. Let Images Be Flexible

    Allow the image to adjust dynamically with the container. Update your .img-contain style like this:

    .container > .img-contain {
        width: 100%;
        border-radius: 15px;
    }
    

    This ensures the image adapts to different screen sizes without breaking the layout. 🌐


    6. Avoid Misuse of position: absolute

    While absolute positioning has its uses, it was applied incorrectly here. Focus on using it only when truly necessary, and ensure it's balanced with parent context styles to avoid layout issues.


    You've done an amazing job so far! With these adjustments, your design will be more robust, responsive, and scalable. Keep up the great work, and feel free to reach out if you have any questions! 🙌

    Best regards,
    Aakash Verma

  • Thapelo Petrick Sikhosana•120
    @Thapelo12345
    Posted 6 months ago

    the design deos not look exactly like the original, the problem is the width one the original is a little bit wider.

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