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

Order summary component

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

Solution retrospective


I found this harder than I thought I would. The positioning of the different divs took a while to get a hang of Working on a challenge instead of being led through a project is much harder but I think it'll really help me learn

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Majito•30
    @Majito1507
    Posted almost 3 years ago

    Hola!

    El posicionamiento de los div también me resultaba difícil, te recomiendo que leas sobre flexbox eso me a ayudado mucho.

    1. Pude observar que para la fuente colocas los link de Google Fonts en tu archivo html, pero en el css no lo colocas(si no vi mal) por eso no te detecta la letra, (font-family: 'Red Hat Display', sans-serif;) este seria la linea que te falto seria en el body para que se aplique en todo el cuerpo.

    2. la siguiente linea en tu archivo HTML : (<div class="order-slip">) la puedes sustituir por una etiqueta main (especifíca el contenido principal de un documento)ejemplo: (<main class="contenedor">), y la podrías usar en css para crear la caja principal que contendrá toda la información.

    3. En la sección de cancelar orden, al momento del hover no le coloques un background-color, en vez de eso solo cambia el color del texto.

    4. En el hover del botón de pago lo puedes colocar una opacidad y ya no es necesario que coloques el color ya que se mantendría el mismo que colocaste en la clase ejemplo: proceed:hover {opacity: 0.7;}

    Espero te sirvan mis observaciones, y más que todo que me haya dado a entender. Puedes pasarte por mi perfil y revisar el código del reto que ya lo culminé, no soy experta en esto pero sigo aprendiendo.

    ¡ÉXITOS!

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