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

Order Summary Card Using Flexbox

Doğukan•60
@dogukan0055
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there again! Sorry for the inconvenience. I made a mistake back then and it wasn't showing the right solution. I can say that I'm new around here, and can't spare much time for challenges but I'm trying my best. I've asked it before but gotta ask it again. How do you guys keep yourself motivated on coding knowledge? I feel like I'm really slow and couldn't learn much. And I know that I've wasted my time watching videos over and over and not doing many challenges, and frontendmentor's challenges are the best practice for overcoming this issue.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Toprak•60
    @toprakunal
    Posted almost 3 years ago

    Hey Doğukan! When i think i'm slow and coudn't learn much and feel demotivated, i always remember the quote " Rome wasn't built in a day ". Just keep consistent and try your best, don't worry about being slow. Addition to that you may consider use media queries for mobile size background image. Keep it up!

    Marked as helpful
  • Account deletedPosted almost 3 years ago

    Hey @dogukan0055, great job on this project!

    Some suggestions to improve you code:

    • To make CSS Variables (:root) easier to deal with, you can give the custom names, like "b--background", "button-color", etc...

    • To properly center your content to your page, add the following to your <body> element:

    body {
        min-height: 100vhh;
        display: flex;
        flex-direction: column ;
        justify-content: center;
        align-items: center 
    }
    
    • While having interactive content (cards, links, icons, buttons, etc…) can definitely make content less static, if not done properly, it can actually have negative effect on your users experience. By simply just applying a “hover” effect to your content, you’re assuming that every device is compatible with “hover” effects. Unfortunately, most devices are not. To provide your users a better experience, you can use the @media (hover: hover) . Now users that that are devices that are not “hover” compatible will be able to enjoy your content.

    Sources:

    https://css-tricks.com/solving-sticky-hover-states-with-media-hover-hover/

    https://youtu.be/uuluAyw9AI0

    Happy Coding!

    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

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