Add Spanish translations for 6 blog posts (2025)

[Copilot]

Adds Spanish (es) translations for six English blog posts from 2025, placing them under content/es/posts/ per the repo's existing multilingual content structure (contentDir: content/es).

New files

ES filename	Original	Date
creando-una-redireccion-de-url.md	hugo-url-redirect.md	2025-11-14
carrusel-deslizante-mejorado.md	carousel-slider-improved.md	2025-10-23
carrusel-automatico-anadido.md	automatic-carousel-added.md	2025-09-11
clases-de-body-utiles.md	useful-body-classes.md	2025-07-09
busqueda-con-lunr-js.md	search-with-lunr-js.md	2025-07-02
pasos-de-migracion-para-v-0-147-9.md	migration-steps-for-v-0-147-9.md	2025-07-01

Conventions followed

• Front matter date preserved verbatim; title translated to Spanish.
• Filenames are Spanish-slugified, matching the pattern of existing ES translations (e.g. mejorando-lightbox.md, redimensionar-todas-las-imagenes.md).
• All code blocks, Hugo template snippets, shortcodes, and URLs left untouched — only prose translated.

Original prompt

Repo: jhvanderschee/hugocodex.

Task: Translate the following existing blog posts into Spanish (ES) and commit them on a new branch.

Posts to translate (by date/title):

• 2025/11/14 - Creating a URL Redirect
• 2025/10/23 - Slider carousel improved
• 2025/09/11 - Automatic carousel added
• 2025/07/09 - Useful body classes
• 2025/07/02 - Search with Lunr.js
• 2025/07/01 - Migration steps for Hugo v0.147.9

Requirements:

1. Locate the source content files for each post in the repository (likely Hugo content under content/ or similar).
2. Create Spanish versions using Hugo's multilingual content conventions used in this repo (e.g., language subfolders like content/es/..., or filename suffixes like .es.md). Follow the repo’s existing pattern.
3. Preserve front matter keys/metadata; translate human-visible fields (title, summary/description, headings, body text) to Spanish. Keep code blocks, shortcodes, links, and filenames/paths intact unless they are part of visible prose.
4. Ensure translated pages keep the same publish date and slug/permalink behavior as the originals.
5. Add only the necessary new/updated files.
6. Create a new git branch (name it something like translate-posts-es-2025 or similar) and commit changes there.

Output: A pull request is not requested; just push the branch with the translations.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: translate this posts onto ES, put them in a new branch

2025/11/14 - Creating a URL Redirect
2025/10/23 - Slider carousel improved
2025/09/11 - Automatic carousel added
2025/07/09 - Useful body classes
2025/07/02 - Search with Lunr.js
2025/07/01 - Migration steps for Hugo v0.147.9

Assistant: I’m waiting for you to confirm the prompted action so I can proceed to create a new branch and add the Spanish (ES) translations for those six posts in jhvanderschee/hugocodex.

This pull request was created from Copilot chat.