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

Results Summary Component Hecho con HTML, CSS y JS con JSON

Benjamin Juarez•390
@ImBenja
A solution to the Results summary component 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?

Frontend Mentor - Solución del componente de resumen de resultados

Esta es mi solución al desafío Results summary component de Frontend Mentor.

📖 Descripción general

El desafío

Los usuarios deben poder:

  1. Ver el diseño óptimo según el tamaño de pantalla de su dispositivo.

  2. Ver los estados de hover y focus en los elementos interactivos.

Bonus: Usar datos de un archivo JSON para cargar el contenido dinámicamente.

Screenshot

Vista de escritorio

Vista móvil

Descripción: Esta son las captura de pantalla de mi solución al desafío Results Summary Component. Muestra la vista de escritorio del componente, con un diseño limpio. Muestra la vista de mobile del componente, con un diseño responsive en todos los dispositivos.

Links
  • Solution URL: Solucion
  • Live Site URL: Sitio en Vivo

🛠️ Mi proceso

Tecnologias utilizadas
  • HTML: Estructura semántica del componente.

  • CSS: Estilos avanzados con Flexbox y gradientes.

  • JavaScript: Uso de Fetch API para cargar datos dinámicos.

  • Google Fonts: Fuente Hanken Grotesk para un diseño moderno.

  • Styled Components - For styles

Lo que Aprendi
  1. Diseño responsive: Usé media queries y un enfoque mobile-first para adaptar el diseño a diferentes dispositivos.

  2. Manipulación del DOM: Aprendí a cargar datos dinámicos desde un archivo JSON.

To see how you can add code snippets, see below:

<div class="card light-red">
  <div class="card__info">
    <p class="card__text--title light-red"></p>
  </div>
  <div class="card__text">
    <p class="card__text--result"></p>
    <span class="card__text--objetivo">/ 100</span>
  </div>
</div>
const categories = document.querySelectorAll(".card__text--title");
const results = document.querySelectorAll(".card__text--result");
const cardInfos = document.querySelectorAll(".card__info");

fetch("./data.json")
  .then((response) => response.json())
  .then((data) => {
    data.forEach((item, index) => {
      if (categories[index] && results[index] && cardInfos[index]) {
        const img = document.createElement("img");
        img.src = item.icon;
        img.alt = item.category;

        cardInfos[index].insertBefore(img, categories[index]);

        categories[index].textContent = item.category;
        results[index].textContent = item.score;
      }
    });
  })
  .catch((error) => console.error("Error:", error));
Desarrollo futuro

En futuros proyectos, me gustaría profundizar en:

  1. Accesibilidad: Mejorar la compatibilidad con lectores de pantalla y cumplir con WCAG.

  2. Animaciones CSS: Añadir transiciones y efectos para mejorar la experiencia del usuario.

  3. Testing: Implementar pruebas unitarias y de integración.

  4. Optimización: Minificar y comprimir los archivos para mejorar el rendimiento.

👨‍💻 Autor

  • GitHub - ImBenja
  • Frontend Mentor - @ImBenja
  • Instagram - @benjajuarez1_

🙏 Agradecimientos

Agradezco a Frontend Mentor por proporcionar este desafío y a la comunidad por su apoyo y feedback.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Benjamin Juarez's solution.

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.