i18n(es): add version guides 0.1.0 beta 31, 0.1.0, 0.2.0 and 0.3.0#232
Merged
Conversation
New files: - api-endpoint.mdx - index.mdx - javascript-helpers.mx
New files: - api-endpoint.mdx - index.mdx - javascript-helpers.mx
- JSDoc comments should remain in English for built-in service implementations. - Spanish capitalization rule violated in three H4 headings. - Spanish documentation should use the English method name to match the actual package source.
Co-authored-by: Adam Matthiesen <amatthiesen@outlook.com>
- /src/content/docs/es/plugins/renderers.mdx - And plugins (small translations in folder /src/content/docs/es/package-catalog/studiocms-plugins/): - sudiocms-auth0.mdx - sudiocms-cloudinary-js.mdx - sudiocoms-discord.mdx - sudiocoms-github.mdx - sudiocoms-google.mdx - sudiocms-html.mdx - sudiocms-md.mdx
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: paul valladares <85648028+dreyfus92@users.noreply.github.com>
Dokploy Preview Deployment
|
Contributor
📝 WalkthroughWalkthroughAdds four new Spanish upgrade guide documents for StudioCMS versions 0.1.0-beta.31, 0.1.0, 0.2.0, and 0.3.0 describing breaking changes, migration steps, bug fixes, and configuration/CLI/database updates. Changes
Sequence Diagram(s)(none — changes are documentation additions only) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 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: 9
🧹 Nitpick comments (1)
src/content/docs/es/guides/upgrade/version-guides/0-3-0.mdx (1)
8-10: Translate the badge text to Spanish for consistency.The badge text should be
NUEVOinstead ofNEW. Other Spanish documentation pages in the storage-api section consistently use Spanish badge labels (text: NUEVO), matching the pattern established for French (NOUVEAU) and English (NEW) versions of the same pages.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/es/guides/upgrade/version-guides/0-3-0.mdx` around lines 8 - 10, Update the frontmatter badge value so the Spanish page uses a Spanish label: change the badge block where it reads "badge:" with "text: NEW" and "variant: success" to use "text: NUEVO" (keep "variant: success" unchanged) so the badge matches other Spanish docs.
🤖 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/guides/upgrade/version-guides/0-1-0-beta-31.mdx`:
- Line 28: Replace the phrase "Dinámica inyección de componentes y scripts en el
panel de control a través de nuevos hooks de plugins." with the corrected
Spanish word order "Inyección dinámica de componentes y scripts en el panel de
control a través de nuevos hooks de plugins." so the adjective follows the noun
("Inyección dinámica") in the sentence.
- Line 72: The text inside the ReadMore component contains a double space ("Ir a
[Variables..."); update the string in the ReadMore element to remove the extra
space so it reads "Ir a [Variables de
entorno](/es/start-here/environment-variables/)..." (locate the ReadMore
component in the file and fix the spacing in its children text).
- Line 45: The bullet point "Introducidas nuevas utilidades de depuración para
facilitar el acceso a información útil de depuración" is missing a period at the
end; update that list item (the exact sentence string) to append a trailing
period so it matches the punctuation of the other items in the list.
- Line 110: Replace the word "lenguaje" with "dialecto" in the sentence that
currently reads "Esta herramienta leerá tu `studiocms.config.mjs` para hacer
posible la conexión con el correspondiente lenguaje de tu base de datos" so it
matches the wording used earlier (and Kysely terminology); update that sentence
to use "dialecto" to ensure consistent terminology across the document.
- Around line 84-88: The text uses "lenguaje(s)" inconsistently for Kysely's
database dialect; update the Aside component title and occurrences of "lenguaje"
within this section to "dialecto" (and plural "dialectos") so terminology
matches the code and Kysely's `dialect` identifier—specifically change the Aside
title "Lenguajes de bases de datos" to "Dialectos de bases de datos" and replace
inline uses of "lenguaje" with "dialecto" (and "lenguajes" with "dialectos") in
the surrounding paragraph and the numbered instruction that mentions client
packages.
In `@src/content/docs/es/guides/upgrade/version-guides/0-1-0.mdx`:
- Around line 38-51: Standardize trailing punctuation in the upgrade notes by
adding a period to bullet lines missing one: append a period to "Implementa un
nuevo sistema de renderizado FolderTree y actualiza la barra lateral interna de
gestión de contenido", "Arregla el problema con la información de depuración que
tenía salidas no disponibles durante PROD", "Asegura que el elemento
personalizado DB Studio esté definido si no está presente la barra de
herramientas de desarrollo", and "Reemplaza todas las instancias de
`.returning()`/`returningAll()` con transacciones para soportar adecuadamente
los dialectos SQL que no soportan retornar como MySQL" so every bullet ends
consistently with a period.
- Around line 35-37: Arregla la indentación inconsistente en los sub-items del
bloque de bullets: alinea la línea que comienza con "- Consulta la
[Documentación de la API de Almacenamiento](/es/storage-api/)" para que use
exactamente 2 espacios como la línea anterior ("- Esta nueva API
proporciona...") (y elimina espacios finales innecesarios) de modo que ambos
bullets queden como hermanos y no uno anidado más profundo.
- Around line 55-57: The ReadMore link currently points to the beta section;
update the anchor in the ReadMore component's Changelog link so it targets the
v0.1.0 release section by replacing the href fragment "#010-beta32" with "#010"
in the line containing the
[Changelog](/es/guides/upgrade/release-notes/#010-beta32) reference.
In `@src/content/docs/es/guides/upgrade/version-guides/0-3-0.mdx`:
- Line 27: Replace the typo "Remplaza" with the standard Spanish "Reemplaza" in
the heading/sentence that reads "Remplaza `chalk` con `styleText` de `node:util`
para StudioCMS CLI" so it matches the terminology used elsewhere (e.g.,
"Reemplazado"); update the text in the MDX content of the node to "Reemplaza
`chalk` con `styleText` de `node:util` para StudioCMS CLI".
---
Nitpick comments:
In `@src/content/docs/es/guides/upgrade/version-guides/0-3-0.mdx`:
- Around line 8-10: Update the frontmatter badge value so the Spanish page uses
a Spanish label: change the badge block where it reads "badge:" with "text: NEW"
and "variant: success" to use "text: NUEVO" (keep "variant: success" unchanged)
so the badge matches other Spanish docs.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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/guides/upgrade/version-guides/0-1-0-beta-31.mdx`:
- Line 123: Update the Spanish text to follow RAE guillemet rules by removing
inner spaces inside the chevrons: replace occurrences of « Migrate to Latest »
with «Migrate to Latest» (and any other instances flagged, there are two) so the
guillemets contain the text without surrounding spaces.
---
Duplicate comments:
In `@src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-31.mdx`:
- Around line 84-88: Update the terminology from "lenguaje(s)" to "dialecto(s)"
in the documented strings: change the Aside title "Lenguajes de bases de datos"
and its body text (the sentence that currently says "lenguaje correcto" and
"libsql si no se especifica ningún lenguaje") as well as the occurrence on the
"6. **Instala los paquetes de clientes de base de datos necesarios**" section
and the mention at line 110 to use "dialecto" (matching Kysely's `dialect`
identifier); keep the already-correct uses at lines 74 and 79 as-is to maintain
consistency.
In `@src/content/docs/es/guides/upgrade/version-guides/0-1-0.mdx`:
- Around line 38-51: Los puntos de la lista en la sección de cambios (en las
líneas que comienzan con "Implementa un nuevo sistema de renderizado
FolderTree...", "Implementa la gestión de taxonomías...", "Implementa nueva UI
de registro de componentes..." y "Asegura que el elemento personalizado DB
Studio..." — así como cualquier viñeta anidada bajo "Implementa la gestión de
taxonomías...") carecen de un punto final; edita el archivo 0-1-0.mdx para
añadir un punto terminal a cada viñeta inconsistente para que todas las entradas
de la lista terminen con un punto y mantener la puntuación homogénea.
dreyfus92
approved these changes
Feb 22, 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
4 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.
Added 4 missing files
Summary by CodeRabbit