i18n(es): update last batch of outdated docs#225
Merged
Conversation
Dokploy Preview Deployment
|
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughSpanish "start-here" docs were reorganized: configuration examples were condensed, ASTRO_DB_* env vars replaced with provider-specific Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Member
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/es/start-here/environment-variables.mdx`:
- Line 15: Replace the stale reference "Astro DB" in the paragraph with wording
that reflects the migration to provider-specific databases; update the sentence
to say something like "establecer una conexión segura a tu base de datos
(libSQL, MySQL o PostgreSQL) y autenticarte con la API de StudioCMS" so the text
no longer mentions "Astro DB" and instead lists the supported providers.
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Around line 401-403: The Aside component's title is still in English
("Supported S3 Providers"); update the title prop on the Aside element (Aside
type="tip" title="Supported S3 Providers") to its Spanish equivalent — e.g.,
title="Proveedores S3 compatibles" — so the aside title is fully translated into
Spanish while leaving the body text unchanged.
- Around line 39-41: Replace the formal English "Use" with the informal Spanish
"Usa" inside the Aside widget so the text matches the document's "tú" tone:
update the Aside component (Aside type='tip' title='StudioCMS Coupon') line from
"Use el código `STUDIOCMS10`..." to "Usa el código `STUDIOCMS10`..." to maintain
consistent verb form across the file.
- Around line 489-491: The sentence in the Spanish doc contains a missing word
after "obtener"—update the phrase that currently reads "para obtener y un
[plugin de renderizado...]" to include the missing object (e.g., "contenido") so
it reads "para obtener contenido y un [plugin de renderizado de StudioCMS]..."
ensuring the sentence flows correctly in the paragraph describing using the
SDK/API and renderer plugin.
- Around line 17-21: In the Aside component block (Aside type="caution"
title="Atención") replace both occurrences of the incorrect masculine article
"Este guía" with the correct feminine "Esta guía" so the Spanish reads "Esta
guía fue recientemente revisada..." and "Si has leído previamente esta guía..."
to fix the grammatical gender error.
In `@src/content/docs/es/start-here/why-studioCMS.mdx`:
- Line 20: Translate the English sentence in the bold line "**Solución de Base
de Datos Personalizada:** Powered by [Kysely](https://kysely.dev/), StudioCMS
works with multiple database dialects including libSQL, MySQL, and PostgreSQL,
with the flexibility to add more as needed." into Spanish, keeping the bold
title and the Kysely link intact and leaving dialect names (libSQL, MySQL,
PostgreSQL) unchanged; replace the English text after the colon with a concise
Spanish equivalent (e.g., "Impulsado por [Kysely](https://kysely.dev/),
StudioCMS es compatible con varios dialectos de bases de datos, incluidos
libSQL, MySQL y PostgreSQL, y permite agregar más según sea necesario.").
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
src/content/docs/es/start-here/getting-started.mdx (1)
262-262: Inconsistent Badge text language.Line 371 uses Spanish (
Añadido en v0.1.0) while lines 262, 292, and 343 keep English (Added in beta.31,Added in beta.22,Revised beta.23). Consider making all Badge labels consistent — either all in Spanish or all in English.Also applies to: 292-292, 343-343, 371-371
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/es/start-here/getting-started.mdx` at line 262, Update the inconsistent Badge label language in the docs by choosing one language (Spanish or English) and making all Badge text values consistent: replace occurrences of "Added in beta.31", "Added in beta.22", and "Revised beta.23" (Badge component usages in the file) to match the Spanish "Añadido en v0.1.0" style (or vice versa if you pick English) so every <Badge text='...'> in this document uses the same localized string.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Around line 496-498: Change the formal imperative "Consulte" to the informal
"Consulta" inside the ReadMore component text (the string starting "Consulte las
[Guías de Frontend Personalizado]...") so it matches the rest of the document's
tú conjugation; update that literal text within the ReadMore component in
src/content/docs/es/start-here/getting-started.mdx.
- Around line 89-95: Replace the English placeholder "port" with the Spanish
"puerto-de-tu-base-de-datos" in the .env example placeholders so they match the
other translated tokens; specifically update the CMS_MYSQL_PORT placeholder in
the MySQL block and the CMS_PG_PORT placeholder in the PostgreSQL block to use
"puerto-de-tu-base-de-datos" instead of "port-de-tu-base-de-datos" or "port".
In `@src/content/docs/es/start-here/why-studioCMS.mdx`:
- Line 20: In the sentence starting "**Solución de Base de Datos
Personalizada:** Impulsada por [Kysely](https://kysely.dev/), StudioCMS funciona
con múltiples dialectos de base de datos incluyendo libSQL, MySQL y PostgreSQL,
con la flexibilidad de añadir más según sea necesario." add a comma before
"incluyendo" so it reads "dialectos de base de datos, incluyendo libSQL..." and
remove the stray trailing space after the final period; update that exact
line/text accordingly.
---
Duplicate comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Around line 39-41: The tip uses the formal Spanish verb "Use" while the
document uses the informal "tú" form; update the Aside component's title/content
so the sentence reads with the informal imperative "Usa" (e.g., change "Use el
código `STUDIOCMS10`..." to "Usa el código `STUDIOCMS10`...") in the Aside
component to match the rest of the document's tone.
- Around line 17-21: La sección del Aside titulado "Atención" tiene errores de
concordancia de género y orden de palabras; cambia "este guía fue recientemente
revisada" y "Si has leído previamente este guía" por "esta guía fue
recientemente revisada" y "Si has leído previamente esta guía", y reordena la
referencia en la última frase para usar el artículo femenino correcto y posición
natural: "consulta la guía [Actualizar StudioCMS a la última
versión](/es/guides/upgrade/latest/) para más información."
---
Nitpick comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Line 262: Update the inconsistent Badge label language in the docs by choosing
one language (Spanish or English) and making all Badge text values consistent:
replace occurrences of "Added in beta.31", "Added in beta.22", and "Revised
beta.23" (Badge component usages in the file) to match the Spanish "Añadido en
v0.1.0" style (or vice versa if you pick English) so every <Badge text='...'> in
this document uses the same localized string.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Line 119: The Spanish sentence "Estás ahora listo para pasar a crear tu
proyecto StudioCMS!" is missing the opening inverted exclamation mark; update
that string to include it so it reads "¡Estás ahora listo para pasar a crear tu
proyecto StudioCMS!" to comply with Spanish punctuation rules.
- Around line 405-413: The S3 .env example uses English placeholder text (e.g.,
CMS_S3_ACCESS_KEY_ID=<your-access-key-id>,
CMS_S3_SECRET_ACCESS_KEY=<your-secret-access-key>,
CMS_S3_BUCKET_NAME=<your-bucket-name>) which is inconsistent with the Spanish
placeholders used elsewhere; update the placeholders in this .env code block to
Spanish equivalents (for example replace <your-access-key-id> with
<tu-access-key-id> or better Spanish wording like <tu-id-de-acceso>, replace
<your-secret-access-key> with <tu-clave-secreta>, and <your-bucket-name> with
<tu-nombre-del-bucket>), and keep the commented optional keys (CMS_S3_ENDPOINT,
CMS_S3_REGION, CMS_S3_FORCE_PATH_STYLE, CMS_S3_PUBLIC_ENDPOINT) using the same
Spanish phrasing style so the .env block matches the rest of the document.
- Around line 351-369: Translate the remaining English strings in the OAuth
section: replace "paths" with "rutas" in the two headings/lines near
"Configurando la URL de devolución de llamada" and "Ejemplos de paths de URL de
devolución de llamada"; localize the first table headers and values by changing
"Environment" → "Entorno", "Callback URL" → "URL de devolución de llamada",
"Production" → "Producción", and "Testing & Dev" → "Pruebas y Desarrollo";
localize the second table headers by changing "Provider" → "Proveedor" and
"Callback PATH" → "Ruta de devolución de llamada" while keeping the provider
rows as-is.
---
Duplicate comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Around line 17-21: In the Aside titled "Atención" update the Spanish grammar:
change "este guía" to "esta guía" and restructure the sentence that references
the link so the article and noun precede the link (e.g., "por favor consulta la
guía [Actualizar StudioCMS a la última versión](/es/guides/upgrade/latest/) para
más información") to fix the mismatched gender and dangling article; locate and
edit the Aside component content around the title "Atención" to apply these
changes.
- Around line 89-95: Replace the English placeholder for the MySQL port in the
.env example so it matches the Spanish PostgreSQL example: update the
CMS_MYSQL_PORT placeholder from "<port-de-tu-base-de-datos>" (currently
"<port-de-tu-base-de-datos>" in the snippet) to the Spanish
"<puerto-de-tu-base-de-datos>" ensuring the CMS_MYSQL_PORT line uses the
corrected Spanish placeholder to maintain consistency.
- Around line 39-41: The Tip Aside titled 'Cupón de StudioCMS' uses the formal
imperative "Use el código"; change this to the informal tú form "Usa el código"
so it matches the document's consistent informal tone — update the string inside
the Aside block (the text `Use el código `STUDIOCMS10`...`) to `Usa el código
`STUDIOCMS10`...` to fix the verb form inconsistency.
In `@src/content/docs/es/start-here/why-studioCMS.mdx`:
- Line 20: In the Spanish copy inside
src/content/docs/es/start-here/why-studioCMS.mdx, add a comma before the gerund
phrase "incluyendo" in the sentence that starts with "**Solución de Base de
Datos Personalizada:** ... dialectos de base de datos incluyendo libSQL, MySQL y
PostgreSQL" so it reads "...dialectos de base de datos, incluyendo libSQL, MySQL
y PostgreSQL"; update that sentence text accordingly to include the comma.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Around line 343-349: The text uses non-standard casing "oAuth" in the section
heading and body (e.g., the header "Opcional: Configurar la autenticación oAuth"
and the two occurrences in the paragraph text and ReadMore label); update every
instance of "oAuth" to the correct IETF capitalization "OAuth" so the heading
becomes "Opcional: Configurar la autenticación OAuth" and the body/ReadMore
references likewise, preserving surrounding punctuation and formatting.
- Around line 262-343: Update the three Badge texts that are in English to match
the Spanish localization: replace "Added in beta.31" with "Añadido en beta.31"
in the heading after "Configurar el dialecto de la base de datos de StudioCMS"
(Badge text currently 'Added in beta.31'), replace "Added in beta.22" with
"Añadido en beta.22" in the heading after "Configurar el renderizado de
StudioCMS" (Badge text currently 'Added in beta.22'), and replace "Revised
beta.23" with "Revisado en beta.23" (or "Revisado en beta.23" style matching
Spanish) in the heading "Opcional: Configurar la autenticación oAuth" (Badge
text currently 'Revised beta.23') so all badges use Spanish phrasing consistent
with the existing "Añadido en v0.1.0".
---
Duplicate comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Around line 89-95: Update the MySQL .env example so the placeholder for port
is translated to Spanish to match the PostgreSQL block: change the
CMS_MYSQL_PORT value placeholder from "<port-de-tu-base-de-datos>" to
"<puerto-de-tu-base-de-datos>" in the getting-started .env code block (look for
the CMS_MYSQL_PORT line in the file's .env snippet) so all placeholders are
consistently localized.
- Around line 353-369: Update the untranslated English strings in the OAuth
callback section: replace "paths" with "rutas" wherever used (including the
sentence "La URL de devolución de llamada debe ser establecida en uno de los
siguientes paths basado en tu entorno"), change the table row labels
"Production" → "Producción" and "Testing & Dev" → "Pruebas y Desarrollo", update
the heading "Ejemplos de paths de URL de devolución de llamada" to use "rutas"
(e.g., "Ejemplos de rutas de URL de devolución de llamada"), and change the
table column header "**PATH** de devolución de llamada" to "Ruta de devolución
de llamada"; ensure the provider example rows remain unchanged except for header
wording.
- Around line 39-41: The Aside component with title 'Cupón de StudioCMS' uses
the formal verb "Use" inconsistent with the document's informal "tú" tone;
change the text from "Use el código `STUDIOCMS10` para obtener un 10% de
descuento para 12 meses de Turso." to the informal form "Usa el código
`STUDIOCMS10` para obtener un 10% de descuento para 12 meses de Turso." so the
wording matches the rest of the document.
- Around line 17-21: Fix two Spanish grammar issues inside the Aside block:
change the incorrect masculine article "este guía" to the feminine "esta guía"
in the sentence that begins "Si has leído previamente…", and move/adjust the
noun and article around the link so the phrase reads correctly (e.g., "por favor
consulta la guía [Actualizar StudioCMS a la última versión] para más
información" or "por favor consulta la guía [Actualizar StudioCMS a la última
versión] para más información") so "guía" is not dangling after the link; update
the Aside content accordingly.
Contributor
There was a problem hiding this comment.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@src/content/docs/es/start-here/getting-started.mdx`:
- Around line 89-95: Replace the English placeholder in the MySQL .env example:
change the CMS_MYSQL_PORT value from "<port-de-tu-base-de-datos>" to the Spanish
"<puerto-de-tu-base-de-datos>" so the CMS_MYSQL_PORT line matches the Spanish
placeholder used in the PostgreSQL block and keeps examples consistent.
- Around line 39-41: Cambiar la palabra formal "Use" por la forma informal "Usa"
dentro del componente Aside titulado 'Cupón de StudioCMS' (la línea que contiene
"Use el código `STUDIOCMS10`...") para que coincida con el resto del documento
que emplea el registro de "tú".
- Around line 343-369: Update the OAuth section text: change all occurrences of
"oAuth" to the standardized "OAuth" (e.g., in the heading "Opcional: Configurar
la autenticación oAuth" and body text), change the badge text "'Versión beta
revisada.23'" to "Revisado en beta.23" to match sibling badges, translate table
environment labels "Production" → "Producción" and "Testing & Dev" → "Pruebas y
Desarrollo", and replace "paths"/"PATH" with Spanish equivalents "rutas" and
"Ruta de devolución de llamada" (ensure examples like
`/studiocms_api/auth/github/callback` keep the same path values).
- Around line 17-21: In the Aside component text, fix two Spanish grammar
issues: change "Si has leído previamente este guía" to "Si has leído previamente
esta guía" (replace "este" with "esta"), and correct the phrase around the
upgrade link by removing the dangling article/word and making the article agree
— replace "consulta el [Actualizar StudioCMS a la última versión](...) guía para
más información" with "consulta la [Actualizar StudioCMS a la última
versión](...) para más información" or alternatively "consulta la guía
[Actualizar StudioCMS a la última versión](...) para más información" so the
article "la" matches "guía" and the link text is not left orphaned.
Adammatthiesen
approved these changes
Feb 19, 2026
This was referenced Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Updates last batch of outdated docs
Summary by CodeRabbit