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

Responsive landing page using HTML and Css

web-components
Saidi•70
@Selik254
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 overall design looks good. Make the color more clear.

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

Making the color look exactly like the design given. Making the website responsive.

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

Responsive design.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ortaly•1,190
    @ortalyarts
    Posted about 1 year ago

    Hey @Selik254!

    Congratulations on completing the challenge!

    I have a few suggestions:

    1. I use this Box sizing rule which allow easy working with width when having paddings. Just paste it at the top of your CSS:
    *,
    *::before,
    *::after {
      box-sizing: border-box;
    }
    

    2.div.container - set it to:

    • margin:auto instead of fixed value of 50px. This will place your div in the middle of the screen.
    • max-width: 250px; - this will allow the container to shrink on very narrow screens. As this is the container of the image, the image will match it's width accordingly to it (if you follow the steps below).
    1. The img element:
    • In html alway include alt attribute (for accessibility).
    • Also always include width and height in the html (this is good for the loading of the page). If you want your image to be responsive, you put the maximal value in the html (take this value from the design file) and then handle the "responsiveness" in the CSS (as described below).
    • In CSS set the img to max-width:100%; height: auto; This will make the image match it's container and preserve it's ratio.
    • float: center; is an invalid property, you don't need it.
    1. Fonts -Try using the provided fonts ("Outfit" in this project).
    • It is best practice to use local fonts, meaning you upload the fonts together with the other app files to the server and use @font-face in CSS.
    • You can lear more about it here.
    1. Set the body element to have the background as in the design file: body {background:#d6e1ef; }.

    I hope you find this helpful! Cheers :)

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