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

htmlCss

Ruben Condori Cosme•10
@Nocturnnn32
A solution to the Product preview card 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?

orgullosos de aver recordado y aprender nuevamente

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

un poco batalle con el ingles en el css pero al final se pudo y conocer algunnos atributos que usa el css pero como dije l final se pudo

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

un poco mas de manejo de css y mejorar

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Grid-World•170
    @LiJunXiang1234
    Posted 5 months ago

    Amigo, parece que has encontrado algunos problemas con el idioma. Yo soy de China y también me siento frustrado con el inglés, pero utilizo ChatGPT para ayudarme a traducir y entender. Tal vez podrías pedirle más ayuda a GPT. Además, parece que aún no estás muy familiarizado con CSS y HTML, y tampoco has entendido el propósito de este ejercicio: necesitamos construir un diseño responsivo. Cuando cambio el tamaño de la página o se detecta que se está abriendo en un móvil, el estilo de la página debe cambiar. Además, solo necesitamos un archivo HTML, no dos como lo has hecho tú. Si no lo entiendes, puedes descargar mi código y echarle un vistazo. Tu CSS y HTML también necesitan más práctica. ¡Ánimo! ¡Tu esfuerzo dará frutos! Si tienes algo que no entiendes, también puedes preguntarme.

    Friend, it looks like you've encountered some language issues. I'm from China and also struggle with English, but I use ChatGPT to help me translate and understand. Maybe you can ask GPT for more help. Additionally, it seems like you're not very familiar with CSS and HTML, and you haven't understood the purpose of this exercise: we need to build a responsive layout. When I resize the webpage or detect that it's being opened on a mobile device, the webpage style should change. Also, we only need one HTML file, not two like you made. If you don't understand, you can download my code and take a look. Your CSS and HTML also need more practice. Keep it up! Your effort will pay off! If you have any questions or don't understand something, feel free to ask me.

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