Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Basic HTML and CSS

Daniel•50
@trevisandaniel
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

  • Hassia Issah•50,390
    @Hassiai
    Posted over 2 years ago

    Remove the <br> in yiour first p[aragraph All your content can be contained in one div, seperate the text from the image by cgiving the text-content a div. To center a content on a page specify these in the body{min-height: 100vh; display: flex; justify-content: center; align-items:center;} in the first geive a color of white and a padding value: .first-div{ backgroung-color: hsl(); padding: 1em}. give the second div a padding-top and padding-bottom value: second-div{padding:1.5em 0;} Use rem or em as unit for the width, padding , height and margin value , check out this video for more https://youtu.be/pKX7YnkyR8g After the media query, give the body a percentage width value Hope am helpful, HAPPY CODING

    Marked as helpful
  • Bizzare•1,320
    @godmayhem7
    Posted over 2 years ago

    hey @trevisandaniel your challenge was totally amazing 👏👏,here are some tips to help you better your code; when i went through your code i noticed you only used div-tags, using just div tags in your body-tag for your sections look kinda messy try using other interactive tags like section-tags(<section></section>),main-tag(<main></main>),header-tag(<header></header>),nav-tag(<nav></nav>) and footer-tag(<footer></footer>) these tags are self explanatory and they help out when other people are trying to understand your code better, the rest of your code was okay👌👌, hope this feedback was helpful 👍👍

    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

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