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

Responsive Landing Page Using Flexbox

Tina•10
@ernestina404
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • maia•300
    @maiaflow
    Posted about 3 years ago

    i like how you organized your css with commented out headers, i'm gonna try that next time! nice work Tina!

  • Eric Salvi•1,350
    @ericsalvi
    Posted about 3 years ago

    Hey Tina,

    Great job with your first submission. I love how you implemented the payment buttons' hover shadow effect. Makes it look like you really pressed down on it on hover.

    I few suggestions for future submissions would be to use an accessibility/HTML validator before submitting your work. I use axe DevTools extension in Chrome. Also if you do end up submitting always check the report that gets generated.

    To fix your background images, it has to do with the relative path. If you were to open up one of the images, this is the path you get. This is because of the single dot (or no dot in your actual CSS) at the start, it would need a double dot. So how you have it is that the single dot (or no dot) is in the current directory but the double dot will take you one folder out, which is not the CSS folder but the root folder to go back into the images folder. Confusing!

    I'd just add ../ to the start of each of your CSS image URLs.

    Lastly, I see you are using filters for opacity as well. Looks like they do not play nice with Safari and other browsers. A good rule of thumb is after you are happy with your current CSS, copy it all and paste it into https://autoprefixer.github.io/ which will add required vendor prefixes for incompatible CSS for all browsers. For instance, the filter opacity doesn't work in Safari but after using that tool, it generates the correct prefixes to be compatible with Safari. -webkit-filter: opacity(80%);

    That tool is a great one to bookmark.

    Keep up the momentum and I am looking forward to new submissions from you!

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