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

Product-preview-card-component-main

Sathya D•310
@satzzzzz07
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Folks, trying out responsive design for the first time. Open to feedback and suggestions. Thanks

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello and congratulations finishing this challenge, maybe I can help you with a few tips and fixes for future projects!

    1 - If you want to get your component on the center of the screen, you can get it with just a few lines of CSS, first of all, remove the margins from your .container class, then add to the parent element (the body) a heigth: 100vh and some flex like this:

    body {
       height: 100vh;
       display: flex;
       flex-direction: column;
       align-items: center;
       justify-content: center;
    }
    

    Those styles will get your component into the center of the screen with no need of using margins!

    2 - It seems that your background-image has a fixed size of 400px, when going into a bigger screen, it falls a bit a lot, a great property to fix this kind of issues is background-size: cover with this property it will cover the whole container!

    3 - Regarding the img, try using an html img for this type of cases, you can use the <picture></picture> tags and inside use the <source></source> to define 1 source for each image depending on the screen size!.

    4 - An my last suggestion is to use more html tags like main section aside ... in this project isn't much important but for future projects try to give more semantic tags!

    Anyway this is a nice start for you as a responsive design project, congratulations and I hope that my feedback helped you!

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub