docs: add Spanish README

[webbrain-one]

Adds README.es-ES.md alongside the original documentation.

[qodo-code-review]

PR Summary by Qodo

Add Spanish README (es-ES) documentation

📝 Documentation 🕐 10-20 Minutes

AI Description

• Add a full Spanish (es-ES) README alongside existing project docs.
• Document installation, API usage, options, and error/quality behavior in Spanish.
• Include quality comparison images and Vite WASM setup guidance for Spanish readers.

Diagram

graph TD
  R["Repo docs"] --> ES["README.es-ES.md"] --> A[("docs/assets/quality/*")]
  ES --> D{{"GitHub Pages demo"}}

  subgraph Legend
    direction LR
    _doc["Markdown doc"] ~~~ _asset[("Image assets") ] ~~~ _ext{{"External link"}}
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Centralized i18n docs (single README + language switch)

• ➕ Improves discoverability and consistency across languages
• ➕ Reduces drift risk by structuring translations side-by-side (or via a docs site)
• ➕ Scales better if more languages are expected
• ➖ More setup overhead (docs tooling, routing, or README restructuring)
• ➖ May be unnecessary complexity for a small number of translations

2. Add a translations index and cross-links

• ➕ Low effort improvement: link Spanish README from the main README (and/or a docs index)
• ➕ Makes translations easy to find without changing tooling
• ➖ Still allows content drift if translations aren’t maintained together

Recommendation: Adding a standalone README.es-ES.md is a pragmatic first step and is appropriate if only one translation is planned. If you expect ongoing multilingual support, consider at least adding cross-links (main README ↔ Spanish README) or a small translations index to improve discoverability and reduce long-term drift.

Files changed (1) +219 / -0

Documentation (1) +219 / -0

README.es-ES.mdAdd Spanish README translation (es-ES) +219/-0

Add Spanish README translation (es-ES)

• Introduces a complete Spanish README covering features, installation, API usage (new + legacy), option reference tables, defaults/validation, error-handling policy, quality behavior and comparison, and Vite WASM setup. References existing quality comparison images under docs/assets.

README.es-ES.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 6 rules

1. Broken TOC anchors 🐞 Bug ≡ Correctness

Description

README.es-ES.md’s Table of Contents links use English fragment IDs (e.g., #features, #installation)
that don’t match the Spanish section headings (e.g., “## Características”, “## Instalación”), so TOC
navigation won’t jump to the intended sections.

Code

README.es-ES.md[R7-20]

+## Tabla de Contenidos
+
+- [Características](#features)
+- [Instalación](#installation)
+- [Uso](#usage)
+- [Funciones](#functions)
+- [Opciones](#options)
+- [Valores por Defecto y Validación de Entrada](#defaults-and-input-validation)
+- [Política de Manejo de Errores](#error-handling-policy)
+- [Comportamiento de la Calidad](#quality-behavior)
+- [Comparativa de Calidad](#quality-comparison)
+- [Configuración de Vite para WASM](#vite-setup-for-wasm)
+- [Licencia](#license)
+- [Autor](#author)

Evidence

The TOC entries reference English fragments like #features/#installation, while the document’s
actual headings are Spanish (“## Características”, “## Instalación”), so the fragments won’t match
the heading-derived anchors.

README.es-ES.md[7-23]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`README.es-ES.md` has a Spanish set of headings, but its Table of Contents points to English fragment identifiers (e.g., `#features`). GitHub-style Markdown generates heading anchors from the *heading text*, so these TOC links won’t resolve.

### Issue Context
This is isolated to the newly added Spanish README and affects reader navigation.

### Fix Focus Areas
- README.es-ES.md[7-23]

### Suggested fix
Update each TOC link fragment to match the actual generated anchor for the Spanish heading (or add explicit HTML anchors with the current English IDs).

For example, either:
- Change `[Características](#features)` to link to the generated anchor for `## Características` (e.g., `#características` on GitHub), and similarly for the other sections.

Or:
- Keep the TOC as-is but add explicit anchors before headings, e.g. `<a id="features"></a>` above `## Características`, etc.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Translation not linked 🐞 Bug ⚙ Maintainability

Description

The new Spanish README is not referenced from the primary README (README.MD), so users landing on
the repository README won’t discover the Spanish documentation via an in-repo link.

Code

README.es-ES.md[R1-6]

+# 📷 img-toolkit
+
+Una librería para redimensionar y editar imágenes.
+
+Demo: https://2yh02.github.io/img-toolkit
+

Evidence

README.es-ES.md exists as a new document, but the repository’s primary README content shown at the
top has no link or language selector pointing to it.

README.es-ES.md[1-6]
README.MD[1-20]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
A Spanish README was added, but the primary landing README (`README.MD`) doesn’t link to it, reducing discoverability.

### Issue Context
GitHub renders `README.MD` on the repository landing page; without a link, readers typically won’t find `README.es-ES.md` unless they browse files directly.

### Fix Focus Areas
- README.MD[1-20]
- README.es-ES.md[1-6]

### Suggested fix
Add a simple language selector near the top of `README.MD`, e.g.:
- `- Español: [README.es-ES.md](./README.es-ES.md)`

Optionally add a backlink at the top of `README.es-ES.md`:
- `- English: [README.MD](./README.MD)`

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[qodo-code-review]

1. Broken toc anchors 🐞 Bug ≡ Correctness

README.es-ES.md’s Table of Contents links use English fragment IDs (e.g., #features, #installation)
that don’t match the Spanish section headings (e.g., “## Características”, “## Instalación”), so TOC
navigation won’t jump to the intended sections.

Agent Prompt

### Issue description
`README.es-ES.md` has a Spanish set of headings, but its Table of Contents points to English fragment identifiers (e.g., `#features`). GitHub-style Markdown generates heading anchors from the *heading text*, so these TOC links won’t resolve.

### Issue Context
This is isolated to the newly added Spanish README and affects reader navigation.

### Fix Focus Areas
- README.es-ES.md[7-23]

### Suggested fix
Update each TOC link fragment to match the actual generated anchor for the Spanish heading (or add explicit HTML anchors with the current English IDs).

For example, either:
- Change `[Características](#features)` to link to the generated anchor for `## Características` (e.g., `#características` on GitHub), and similarly for the other sections.

Or:
- Keep the TOC as-is but add explicit anchors before headings, e.g. `<a id="features"></a>` above `## Características`, etc.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[qodo-code-review]

2. Translation not linked 🐞 Bug ⚙ Maintainability

The new Spanish README is not referenced from the primary README (README.MD), so users landing on
the repository README won’t discover the Spanish documentation via an in-repo link.

Agent Prompt

### Issue description
A Spanish README was added, but the primary landing README (`README.MD`) doesn’t link to it, reducing discoverability.

### Issue Context
GitHub renders `README.MD` on the repository landing page; without a link, readers typically won’t find `README.es-ES.md` unless they browse files directly.

### Fix Focus Areas
- README.MD[1-20]
- README.es-ES.md[1-6]

### Suggested fix
Add a simple language selector near the top of `README.MD`, e.g.:
- `- Español: [README.es-ES.md](./README.es-ES.md)`

Optionally add a backlink at the top of `README.es-ES.md`:
- `- English: [README.MD](./README.MD)`

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools