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

Perfume page with some flexbox and grid

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

Solution retrospective


Is it a good idea to center an image using flexbox like this? I'd first tried setting the height/width and margins but it got very messy.

I was at a total loss at the beginning so I looked at others' work, figured out how it was done and then built mine. I'm not sure how else to learn how to do this, but I also don't like "cheating". How do you recommend figuring these out when you're totally stuck?

I don't think my mobile media queries are done well. Is there something obvious I'm missing?

Thanks for any help!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Saulius K.•560
    @TH3RIV
    Posted over 2 years ago

    Hi, @sudaspace!

    Centering using flexbox is perfectly fine and using margins to center something is definitely not the right way IMO. The card looks great in desktop mode, but has problems with mobile. You should always start mobile and then move to desktop.

    Addressing issues with your design:

    • Mobile card is too big and occupies the whole screen, height and width.

    Try setting max-width, adding padding to the body or making the card to not take 100% of the width.

    • The previous price font is wrong and should be the same one as the description.
    • Button needs some work, add a button:hover and cursor styling, so the button is interactive.

    Hope this helps!

    Marked as helpful
  • Rocky•50
    @stallone1
    Posted over 2 years ago

    wow your projects looks awsome follow me so you can see how mine looks i’m going submit mine in an hour how did you manage to get it to mobile version ?

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