Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

very responsive

Victoryobasi•260
@Victoryobasi
A solution to the Product preview card 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?

Responsive design: Works well on various devices and screen sizes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Timothé Bissonnette•480
    @Fable54321
    Posted 10 months ago

    Ok, so i'm not gonna dig too deep into this, but looking at your code, first thing I noticed is that all your css is in your html file using the tag.

    Just type how to link CSS to html on google, it will take you 2 minutes to grasp and it will make your code look much cleaner :).

    Now I don't know if you have noticed, your layout is centered at 1440px, wich shows me you"ve used the width given in the style guide, good job on that. The issue is the layout is not centered on any other widths.

    The more I look at your code the more I realize this might have been a bit of a nightmare for you. Don't worry, not so long ago I wante d to break things trying to center something using CSS.

    The first issue lies in your body selector. I see an align-content. First, align-content is a property that only works on flex containers. Second, I would tell you not to worry with the align-content for now, it is rarely useful.

    What you would need in this case is a display of flex, a justify-content of center and an align-items of center. This will center your layout in realtion to the body. Wich leads me to the fact you have use a fixed height. Now this is fine for a project like this wich you know will never take more than the screen height (at least on desktop), but in other cases you should switch from "height" to a "min-height" of 100vh, this will allow it to "follow" the size for your project.

    If you do all the above steps you wouldn't have the mess I see realted to margins on your container selector, because everything would have been centered from the beggining :).

    So, I won't dig deeper into it, Overall it looks good, the sizes are not exact but the proportions are pretty much kept so it looks good.

    Good job, keep up!

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