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

Responsive card using CSS flex

Rowert Méndez•70
@P0wertDev
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?

My progress in the development world

I pride myself on having the ability to create useful and beautiful web components from scratch with little help.

What I would do differently next time is to use some framework to streamline the process and make it more scalable.

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

Responsive card

My biggest challenge was to create a card that could be adapted to all devices.

I overcame it with media queries

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

I need more help in CSS Flex and CSS Grid, and responsive.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted about 1 year ago

    I noticed some areas where your HTML and CSS code can be improved to make it more efficient:

    HTML:

    1. Using the article tag:

      • Instead of using the main tag as a container for the card, use the article tag and give it the class global_card. You can leave the main tag unchanged.
      • There is no need to use IDs in this project; classes are sufficient.
    2. Improving accessibility with alt:

      • Instead of using the picture tag, use the img tag and don't forget to add the alt attribute to improve accessibility.
    3. Using h1 instead of h2:

      • Since the main title is important, replace the h2 tag with an h1 tag.
      • As for the div that contains the h2 and p tags, you can omit it because h2 and p are block elements by nature, so it's enough to add margin to the h2.

    CSS:

    1. Using max-width and min-height:

      • In the body, add the properties max-width: 100dvw; and min-height: 100dvh;.
      • Instead of using the shorthand background property, use just background-color.
    2. Improving responsiveness:

      • Because you set the card's width to 80%, you might encounter responsiveness issues. It's better to use the max-width property, which will greatly help with making the design responsive.
      • According to the design file, the ideal width for the card is 320px, so use max-width: 320px;.
      • You won't need to use flexbox within the card or text wrap. You can also remove the media queries.

    If you encounter any issues or don't understand something, feel free to let me know.

    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