Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Four-card-feature-section

John Gorman•150
@Johng117
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I think that I managed to implement the grid positioning system quite well. More planning ahead of time in terms of working out the size of typography for each view would have helped as I spent a lot of time tweaking things.

What challenges did you encounter, and how did you overcome them?

Working out how to split the grid up horizontally and vertically was challenging. It took a lot of experimentation and trial and error to work out the best way to do it.

What specific areas of your project would you like help with?

Moving from mobile view to tablet view, how things should look in tablet view.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Farid_Danilo•140
    @FaridDanilo
    Posted about 1 month ago

    Feedback sobre tu solución

    A continuación, te comparto algunos puntos de mejora que pueden ayudarte a perfeccionar aún más tu código:


    HTML

    1. Error semántico en la estructura principal

      • Detecté que estás combinando dos etiquetas en una sola línea:
        <main section class="main-container">
        
      • Corrección: Solo deberías usar una etiqueta en ese lugar. Lo correcto sería:
        <main class="main-container">
        
    2. Jerarquía de títulos

      • Actualmente tienes dos etiquetas <h1>: una para el título y otra para el subtítulo. Recuerda que solo debe haber un <h1> por página para mantener una estructura semántica adecuada.
      • Sugerencia de corrección:
        <h1 class="title-normal">Reliable, efficient delivery</h1>
        <h2 class="title-bolder">Powered by Technology</h2>
        
    3. Encabezados en las tarjetas

      • En cada tarjeta usas <h2> para el título. Para mantener la jerarquía, te recomiendo emplear <h3>, ya que ya tienes <h1> y <h2> para el título principal y subtítulo.
      • Corrección:
        <h3 class="s-title">Supervisor</h3>
        
    4. Nombres de clases CSS

      • Estás utilizando nombres como s-title, tb-info, etc. Si bien funcionan para este proyecto, pueden dificultar la reutilización y escalabilidad del código en proyectos más grandes.
      • Recomendación: Utiliza nombres de clases más genéricos y descriptivos, por ejemplo: card-title, card-info, card-image, etc.

    CSS

    1. Uso de font-family en el selector universal

      • Actualmente tienes:
        * {
          box-sizing: border-box;
          margin: 0;
          padding: 0;
          font-family: "Poppins";
        }
        
      • Es mejor aplicar la fuente en el selector body en vez del universal (*), para evitar posibles conflictos en el futuro.
      • Sugerencia:
        body {
          font-family: "Poppins", sans-serif;
        }
        
    2. Variables CSS

      • Observé que usas variables como --Grey-500. Es recomendable emplear minúsculas y guiones para mantener la coherencia y facilitar la escalabilidad:
        --grey-500
        
      • La consistencia en la nomenclatura hace que el código sea más fácil de mantener y escalar.

    Espero que estos comentarios te sean útiles :)

    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