i18n(es): add 0-1-0-beta-17#132
Conversation
WalkthroughA new Spanish-language documentation page has been added to describe the changes in StudioCMS version 0.1.0-beta.17. The page outlines performance optimizations, bug fixes, and new features such as a comment system in the control panel. It also includes a notice about a password hashing algorithm change introduced in the previous beta, advising users to update their passwords. No major code changes are present; the update is focused on documentation for the upgrade process. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx (3)
2-4: Refine frontmatter description for clarityThe
descriptionfield currently reads:
Actualiza StudioCMS a Beta.17To improve clarity and consistency with other version guides, consider using the full version string and including "versión":
-description: Actualiza StudioCMS a Beta.17 +description: "Actualiza StudioCMS a la versión 0.1.0-beta.17"
13-13: Remove unused importThe
ReadMorecomponent is imported but not used in this file. To keep the code clean, please remove this line:-import ReadMore from '~/components/ReadMore.astro'
27-27: Fix missing accent on "mejoró"In Spanish, the past tense "mejoró" requires an accent on the "o". Please update:
- - Se mejoro la detección de la ruta del archivo clave para el comando CLI [`crypto gen-jwt`](/es/how-it-works/cli/#crypto-gen-jwt). + - Se mejoró la detección de la ruta del archivo clave para el comando CLI [`crypto gen-jwt`](/es/how-it-works/cli/#crypto-gen-jwt).🧰 Tools
🪛 LanguageTool
[misspelling] ~27-~27: Si el verbo está en pasado, se escribe con tilde.
Context: ...ieron problemas con Astro Fonts. - Se mejoro la detección de la ruta del archivo cla...(SE_CREO)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx
[uncategorized] ~23-~23: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...ctualización - Nuevas características - Se añadió un nuevo sistema de comentario...
(AI_ES_GGEC_REPLACEMENT_OTHER)
[misspelling] ~27-~27: Si el verbo está en pasado, se escribe con tilde.
Context: ...ieron problemas con Astro Fonts. - Se mejoro la detección de la ruta del archivo cla...
(SE_CREO)
[uncategorized] ~28-~28: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...-works/cli/#crypto-gen-jwt). - Mejoras - Se reemplazó [lodash](https://www.npmjs....
(AI_ES_GGEC_REPLACEMENT_OTHER)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Run Starlight Link Check
🔇 Additional comments (3)
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx (3)
17-17: Verify localization of QuickUpdate componentThe
<QuickUpdate />component is included here, but please confirm that its internal copy is displayed in Spanish or that it pulls the correct locale data. If it defaults to English, you may need to add a Spanish version or adjust its props.
32-34: Ensure consistent tone in user-facing messagingThe aside uses informal second-person ("ten en cuenta", "te recomendamos") while other docs may adopt an impersonal or formal tone. Please verify the preferred style for Spanish documentation (e.g., impersonal "Recomendamos a los usuarios...") and adjust accordingly.
19-31: Great translation of update summaryThe summary section and bullet points accurately reflect the original English content, and the terminology is consistent (e.g., "panel de control", "optimizado", "procesamiento de niveles de permisos"). No issues spotted apart from the missing accent mentioned above.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~23-~23: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...ctualización - Nuevas características - Se añadió un nuevo sistema de comentario...(AI_ES_GGEC_REPLACEMENT_OTHER)
[misspelling] ~27-~27: Si el verbo está en pasado, se escribe con tilde.
Context: ...ieron problemas con Astro Fonts. - Se mejoro la detección de la ruta del archivo cla...(SE_CREO)
[uncategorized] ~28-~28: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...-works/cli/#crypto-gen-jwt). - Mejoras - Se reemplazó [lodash](https://www.npmjs....(AI_ES_GGEC_REPLACEMENT_OTHER)
Description
Translates
0-1-0-beta-17to spanishSummary by CodeRabbit