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

responsive , flexbox.

Yahia-kilany•90
@Yahia-kilany
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 challenges did you encounter, and how did you overcome them?

the margins were a bit tricky and I had to do a lot of trial and error to be as close as possible to the desgin. but I think I did well

What specific areas of your project would you like help with?

the code is not clean and i am sure there are more efficient ways to improve it

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • beowulf1958•1,890
    @beowulf1958
    Posted 12 months ago

    Congratulations on completing the project. It looks great and is responsive. Looks just like the design in desktop and mobile version.

    The code is well organized and clean--but not DRY. There is something called the DRY principle (Don't Repeat Yourself). Anytime you see yourself repeating the same code in multiple places, it is time to pull it out and create a utility class. For example: both .price and .discounted are styled display: block; this is redundant in an h1, and unnecessary for the span. Similarly, .order is styled both border: 0px and border: none which is redundant.

    You could create two utility classes to save yourself some code.

          .flex-c {
            display: flex;
            align-items: center;
            justify-content: center;
          }
          .accent {
            font-family: "Fraunces";
            font-weight: 700;
          }
    

    You can add "flex-c" to body, .container, and .order-btn (change .order-btn to flex-c). Then add accent to .title and .price. Now you're clean and DRY. Hope this helps

    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