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

Responsive perfume blog with HTML and CSS

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

Solution retrospective


Which is the best way (without using display: flex) to center the container and its contents

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kehinde Hussein, Fasunle•190
    @Fasunle
    Posted over 2 years ago

    Hi @Deem,

    It is my pleasure to review your project. This is good for a starter and you can always become better. I will give a few tips that will help you do a better job.

    • Use can use either grid or flex. However, using flex is more flexible for this simple case. Using float or table is not recommended as this is very painful to scale in real life. That is not to say that they do not have their uses as well.

    • You can use picture tag to manage the two images without worrying about anything. Check this page to learn how to use it: https://www.w3schools.com/htmL/html_images_picture.asp

    • Read about semantic html. This will enable you to know which tag to use under different contexts and also, how they should be arranged/organized. Check: https://www.w3schools.com/htmL/html_images_picture.asp

    • On mobile screen size, ensure that your content does not take too much height. This prevents the image from getting too small (vertically). You can correct it by setting max-height for the content.

    If you find this useful, kindly mark it as helpful.

    Happy coding!!!

  • Vicktor•920
    @Victor-Nyagudi
    Posted over 2 years ago

    Hi, Deeem.

    You can also use display: grid, however, I'm curious why you don't want to use flexbox.

    Is it giving you issues?

    Before grid and flexbox, front-end developers relied on float and clear to position items inside a container. It wasn't always the best, but it got the job done.

    Read more about float and clear here.

    Hope this helps.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub