Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 26 days ago

Todo App | React + Tailwindcss 4|

tailwind-css, react
Gastón Federico Nahuel Gómez•440
@Morfeo1997
A solution to the Todo app 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 was able to adapt quickly to the changes that were applied to Tailwind in their version 4 after some time without using it.

I think I would change the way I do the background so that I don't have to suffer the error that occurs when there are too many tasks and generates that white background that is annoying.

////SPANISH / Español //////

Pude adaptarme rapido a los cambios que aplicaron a Tailwind en su version 4 despues de estar un tiempo sin utilizarlo

Creo que cambiaria la forma del background para que no tenga que sufrir el error que ocurre cuando hay demasiadas tareas y genera ese fondo blanco que resulta molesto.

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

What complicated me (I was 1 whole day) was the change of responsive image and dark mode. It was easily solved by applying css in the respective elements.

///////Spanish / Español ///////

Lo que me complico (estuve 1 dia entero) fue el cambio de imagen responsivo y modo oscuro. Se soluciono facilmente aplicando css en los elementos respectivos.

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

I would like a suggestion on how to make the order of the elements interchangeable, I tried different ways but always generated errors so I ended up eliminating the function in the final version.

By the way, if anyone has any recommendations on how to write a decent readme I would appreciate it very much.

////////Spanish / Español ////////

Me gustaria una sugerencia sobre como lograr que el orden de los elementos puedan ser intercambiables, intente en distintas formas pero siempre me generaron errores asique termine eliminando la funcion en la version final

Por cierto, si alguien tiene alguna recomendacion de como escribir un readme decente se lo agradeceria mucho.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Gastón Federico Nahuel Gómez'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.