Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

Responsive 3-column preview card component with HTML5, CSS3, Flexbox..

accessibility
JERRY COMFORTER ASARE•150
@jcasare
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I struggled a bit with the mobile design as I couldn't get the layout to change to a column view....not knowing I had set the display to grid. What I'd like to know is if I have to write codes for almost every breakpoint in these challenges or just one for desktop and one for mobile?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • King•310
    @rymnddev
    Posted about 3 years ago

    What really helped me is actually designing layouts for mobile first, and then adjusting as necessary for wider screens. Maybe start your next project with that in mind and see if you notice a difference.

    Marked as helpful
  • Zsofia Dalnoki-Papp•210
    @dalnoki
    Posted about 3 years ago

    Hey @jcasare,

    I'm pretty sure that the current solution belongs to the 3-column preview challenge - but this is a solution for the QR code component, that's why the design comparison behaves like this.

    Also, as a general rule of thumb, it's always advised to put your images in an images or assets folder, and also the "Challenge documentation.docx" shouldn't belong to the repo.

    As for the breakpoints: you only get the design for a few resolutions (mostly it is desktop, tablet-portrait, tablet-landscape, and mobile) and you need to make sure that your site behaves well on other resolutions too. You need to adjust your breakpoints accordingly. If you check your project on 568px resolution, the buttons slide out of the card, so you need to look for a solution that works on basically every possible resolution.

    It's also advised to have a "main" HTML element, for example, instead of the <div class="wrapper">.

    I hope this helps, good luck!

    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