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

Responsive product preview card using flexbox

mihai2537•190
@mihai3636
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey, guys!

  • I noticed that I'm always having troubles with deciding what should I explicitly size first: the image itself or its container?
  • for example, my approach was to first ask myself: how big do I want the whole stuff to be (left plus right pannel). Then I set the container width then I figured out that I want the picture to be half of the container so I went and I set a width on the picture. Is there any better approach in scenario like this (left panel image + right panel text)?
  • last question: what would be the best approach to change the img dinamically based on the viewport size? This time I used the html picture tag, do you usually do it differently? I read that there is some way by making it the background image or something.

Thanks for reading, if you see anything else that I did which is fishy, please let me know!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P. Ricardo•2,370
    @pRicard0
    Posted over 1 year ago

    HTML tips

    • Add aria-hidden="true" and focusable="false" to the SVG element to hide it from technologies such as screen readers.
    • Instead of using the tag <p> with the text "$149.99", you can use the <em> tag. The <em> tag is used to define emphasized text. The content inside is typically displayed in italic. A screen reader will pronounce the words in <em> with an emphasis, using verbal stress.
    • You can use the tag <s> instead of the tag <span> with the text "$169.99". The <s> tag specifies text that is no longer correct, accurate or relevant. The text will be displayed with a line through it by default.

    CSS tips

    • You can add transition: 200ms; to your button for a smoother color change.
    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
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