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

1st Project - Order Summary Card (Built with Atom)

Avedi•20
@AvediMusungu
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I would appreciate feedback specifically on the following:

  • How to maintain the sizes of the various elements whenever i zoom in or out.
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Patryk Besler•355
    @beslerpatryk
    Posted almost 4 years ago

    Hey Avedi 👋

    Awesome job, you are doing great. There are, however, few issues that you should work on.

    Responsive units - when working on a project it is a good practice to make sure that the page you are coding looks good on both small and big screen devices. Usually, it is not recommended to define position properties such as the bottom, left, etc. using definitive values. Next time try using percents. You can read more about responsive units here: https://gist.github.com/basham/2175a16ab7c60ce8e001

    I would also recommend you to check out some articles or youtube videos about the mobile-first approach. It might help you with the workflow especially at the beginning of your journey.

    Hope that some of it were helpful. Keep up the good work and good luck on your future projects!

    Marked as helpful
  • Андрій Рогов•1,155
    @Andrii-Rohov
    Posted almost 4 years ago

    Hey, try to delete these props {position: absolute; top: 50px; left: 500px;} from .landing-page and add those instead {margin-top: 100px; margin: auto; min-width: 400px; max-width: 600px;} for start. And try add to body { background-size: cover; or maybe contain;} see how it will affect it

    Marked as helpful
  • devjakov•210
    @devjakov
    Posted almost 4 years ago

    this is not responsive unfortunately, the sizing keeps changing and only looks good on mid screens, above 1080p breaks and under 500p it breaks as well

    The width and the height of the container need to be a fixed size

    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

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