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

My first frontend challenge.

cube-css, express
avigithubb•10
@avigithubb
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Help me If you find anything wrong in this site and could've been better and improved.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • luking•230
    @alululululuer
    Posted over 2 years ago

    Hello! Congratulations on starting your first frontend journey. Give you some advice from my perspective.

    • HTML

      • put your .Outside-box into <main>
      • put your .attribution into <footer>
      • use <h1> instead of <p> for the text "Improve your..." as the accessibility report said that "Page should contain a level-one heading"
    • CSS

      • remove width and height and margin of .Outside-box
      • add max-width to .Outside-box
      • to center the .Outside-box in the body you can use flex or grid layout to instead.
        • for the beginner, I suggest you can use flex layout first.
          • remember to add a height to the body at first.
      html,body {
        height: 100%;
      }
      body {
        display: flex;
        flex-direction: column;
        justify-content: center;
        align-items: center;
      }
      
      • remove width and margin to the <img>, to make <img> fit the .My-img you can do the bottom. Look at the img reset
      img {
        display: block;
        max-width: 100%;
      }
      
      • always follow the style-guide as you can, your second-para's color is poor visibility.👀

    Hope it's helpful to you and happy coding.

  • Neemias araujo•160
    @NeemiasEeep
    Posted over 2 years ago

    hey, this is almost perfect, you can only change the img atributes, like this in this away your image element will be insede your card

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