Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Basic HTML/CSS Excercise

Daniel Dekany•920
@dknyd
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi Guys,

Nothing really to add here, one of my first projects which I just got to upload, pretty straightforward but any feedback is appreciated. :)

Trezmor

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • mateusz96•110
    @mhanak96
    Posted over 2 years ago

    Hi Trezmor!

    I think you should learn about flexbox & grid - which will help you place couple items in one line like in "annual plan" block here and make your websites responsive. Good resources (which are also free) are: WebBos "What the flexbox?" course and Kevin Powell "Conquering responsive layouts", you can also play games like "flexbox froggy" or "grid garden".

    If you want to center your designs i think that the easiest solution is setting your body height, displaying it to grid and centering the items (on x & y axis) inside the grid:

     height: 100vh;
     display: grid;
     place-items: center 
    

    Tip - you can make you button look better by setting border to none (thanks to that this grey border will no longer be present) .

    That's awesome that you are trying to use BEM notation in your css 😉 - it will benefit you in your future css journey when you will be learning sass.

    Good luck and happy coding! 💪

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