i18n(es): translate docs in ecosystem/packages directory#230
Merged
Conversation
Dokploy Preview Deployment
|
Contributor
📝 WalkthroughWalkthroughSeven new Spanish documentation pages added under Changes
Sequence Diagram(s)(omitted — changes are documentation only) Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 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/ecosystem/packages/sdk.mdx (1)
23-25: DuplicateReadMoreblocks pointing to the same URL.Lines 23–25 and lines 46–48 both link to
/es/how-it-works/sdk/with near-identical content. Consider removing one or differentiating them (e.g., keeping only the one in the "Lecturas adicionales" section).Also applies to: 46-48
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/es/ecosystem/packages/sdk.mdx` around lines 23 - 25, There are duplicate ReadMore blocks both linking to /es/how-it-works/sdk/ (the ReadMore component at lines 23–25 and again at 46–48); remove one of them (preferably delete the earlier ReadMore or the non-"Lecturas adicionales" instance) so only the intended "Lecturas adicionales" ReadMore remains, or alternatively change the copy/URL of one to point to a different resource to avoid duplication; locate the ReadMore component instances in src/content/docs/es/ecosystem/packages/sdk.mdx and remove or modify the duplicate.
🤖 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/ecosystem/packages/buildkit.mdx`:
- Line 16: The introductory sentence "Este es un kit CLI basado en esbuild para
construir integraciones Astro" is missing a trailing period; update that line in
src/content/docs/es/ecosystem/packages/buildkit.mdx to end with a period so it
reads "Este es un kit CLI basado en esbuild para construir integraciones Astro."
ensuring punctuation consistency.
- Line 66: The sentence "Para otros tipos de contenido y cómo usarlos, consulte
[la documentación de esbuild](https://esbuild.github.io/content-types/)" is
missing a terminal period; update that string in the Markdown/MDX content so it
ends with a period, i.e. append "." to the sentence text in src content where
the link appears (the exact sentence in buildkit.mdx).
- Around line 50-51: Reemplaza el artículo masculino "Los" por el femenino "Las"
en la oración que empieza "Los siguientes extensiones de archivo..." para que
concuerde con el sustantivo femenino "extensiones" — es decir, cambia esa frase
a "Las siguientes extensiones de archivo se copiarán de su src a sus respectivas
salidas y no se transformarán como si fueran activos estáticos."
In `@src/content/docs/es/ecosystem/packages/cfetch.mdx`:
- Line 17: The introductory sentence "Esta es una [integración de
Astro](https://docs.astro.build/es/guides/integrations-guide/) que proporciona
una función fetch con caché para proyectos Astro SSR" is missing a trailing
period; update that line in src/content/docs/es/ecosystem/packages/cfetch.mdx so
the sentence ends with a period (i.e., append "." to the end of the sentence) to
correct punctuation.
In `@src/content/docs/es/ecosystem/packages/kysely.mdx`:
- Line 18: Fix the spacing in the sentence by adding a space before the
parenthetical so "libSQL(SQLite)" becomes "libSQL (SQLite)"; update the text in
the markdown/MDX content where the phrase appears (the line containing
"Actualmente StudioCMS solo soporta bases de datos libSQL(SQLite), MySQL y
PostgreSQL via Kysely.") to read "libSQL (SQLite)".
- Around line 256-257: The exported function is misnamed `insertUser` while its
implementation and internal variable use `getUserById`; rename the export from
`insertUser` to `getUserById` (update the `export const insertUser =
Effect.gen(...)` declaration to `export const getUserById = Effect.gen(...)`)
and adjust any local references or re-exports that expect `insertUser` so they
now reference `getUserById` (check usages around `getDbClient` / `withCodec` to
ensure imports/exports remain consistent).
In `@src/content/docs/es/ecosystem/packages/markdown-remark.mdx`:
- Line 152: The sentence "Este proyecto está fuertemente basado en y compatible
con el paquete integrado de Astro `@astrojs/markdown-remark`" is missing a
period; update that string by appending a period so the sentence ends with
"…`@astrojs/markdown-remark`." ensuring proper punctuation before the next
heading.
In `@src/content/docs/es/ecosystem/packages/template-lang.mdx`:
- Line 123: Replace the untranslated English section heading "### Default
Values" with its Spanish equivalent to match surrounding headings; locate the
heading string "### Default Values" in the file and change it to "### Valores
predeterminados" (preserve Markdown heading level and spacing).
- Line 17: Translate the English sentence that describes the package into
Spanish: replace the line that reads "`@withstudiocms/template-lang` is a simple
MIT Licensed TypeScript ESM template language for HTML emails, similar to
Handlebars but focused on simplicity and database data integration." with an
equivalent Spanish sentence while keeping the package identifier
`@withstudiocms/template-lang`, license mention (MIT), and technical terms
(TypeScript, ESM, HTML emails, Handlebars) intact so readers can still recognize
the package and functionality.
---
Nitpick comments:
In `@src/content/docs/es/ecosystem/packages/sdk.mdx`:
- Around line 23-25: There are duplicate ReadMore blocks both linking to
/es/how-it-works/sdk/ (the ReadMore component at lines 23–25 and again at
46–48); remove one of them (preferably delete the earlier ReadMore or the
non-"Lecturas adicionales" instance) so only the intended "Lecturas adicionales"
ReadMore remains, or alternatively change the copy/URL of one to point to a
different resource to avoid duplication; locate the ReadMore component instances
in src/content/docs/es/ecosystem/packages/sdk.mdx and remove or modify the
duplicate.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
src/content/docs/es/ecosystem/packages/buildkit.mdx (1)
49-49: Lowercaseassetsin Spanish prose.In Spanish, "Assets" (line 49) is a common noun and should be written in lowercase. The capitalised English form reads as a proper noun.
✏️ Proposed fix
-#### Archivos considerados como Assets +#### Archivos considerados como assets🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/es/ecosystem/packages/buildkit.mdx` at line 49, Update the heading "#### Archivos considerados como Assets" so the noun "Assets" is lowercase in Spanish prose; replace that header with "#### Archivos considerados como assets" (i.e., change the word Assets → assets) to conform to Spanish capitalization rules.
🤖 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/ecosystem/packages/buildkit.mdx`:
- Line 28: The sentence "Una vez que instales el paquete buildkit, ahora tienes
acceso a una utilidad CLI `buildkit`, añade lo siguiente a tus scripts de
integración:" contains a comma splice; split it into two sentences by replacing
the comma before "añade" with a period and capitalizing "Añade" (e.g.,
"...utilidad CLI `buildkit`. Añade lo siguiente a tus scripts de integración:")
so the two independent clauses are properly separated.
In `@src/content/docs/es/ecosystem/packages/template-lang.mdx`:
- Line 17: Update the package description for `@withstudiocms/template-lang` to
correct Spanish grammar: replace "MIT Licenciado" with "con licencia MIT" (or
"bajo licencia MIT") and change "y integración" to "e integración" so the
sentence reads naturally in Spanish and follows the euphony rule before words
beginning with "i"/"hi".
---
Nitpick comments:
In `@src/content/docs/es/ecosystem/packages/buildkit.mdx`:
- Line 49: Update the heading "#### Archivos considerados como Assets" so the
noun "Assets" is lowercase in Spanish prose; replace that header with "####
Archivos considerados como assets" (i.e., change the word Assets → assets) to
conform to Spanish capitalization rules.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/content/docs/es/ecosystem/packages/template-lang.mdx (1)
46-46: Adjective placement makessimpleambiguous."para interpolación de variables simple" places
simpleimmediately aftervariables(feminine plural), so it reads as "simple variables" and would needsimples. Moving the adjective clarifies that it modifiesinterpolación:✏️ Proposed fix
-Está principalmente diseñado para interpolación de variables simple. +Está principalmente diseñado para la interpolación simple de variables.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/es/ecosystem/packages/template-lang.mdx` at line 46, The phrase "para interpolación de variables simple" misplaces the adjective so it appears to modify "variables"; update the sentence in the text that currently reads "A diferencia de otros lenguajes de plantillas, el lenguaje de plantillas de StudioCMS se enfoca en la simplicidad y no incluye lógica compleja o estructuras de control. Está principalmente diseñado para interpolación de variables simple." to place "simple" next to "interpolación" (for example: "Está principalmente diseñado para la interpolación simple de variables" or "Está principalmente diseñado para la interpolación de variables de forma simple") so the adjective clearly modifies "interpolación."
🤖 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/ecosystem/packages/template-lang.mdx`:
- Line 38: The opening sentence has a subject–verb/person mismatch: "Para
aquellos interesados en usar el lenguaje de plantillas de StudioCMS en sus
proyectos, puedes instalarlo usando tu gestor de paquetes preferido:" — either
make the whole sentence third person plural (e.g., change "puedes" → "pueden"
and "tu gestor" → "su gestor") or convert the opener to second person singular
(e.g., change "Para aquellos interesados" → "Si estás interesado" or "Para ti
interesado") so subject and verbs/pronouns agree; update the clause containing
"puedes instalarlo" and "tu gestor de paquetes preferido" accordingly to match
the chosen person.
---
Duplicate comments:
In `@src/content/docs/es/ecosystem/packages/template-lang.mdx`:
- Line 17: In the sentence describing `@withstudiocms/template-lang`, replace
the conjunction "y integración" with "e integración" to follow Spanish euphony
rules (since "integración" begins with "i"); edit the string containing
"`@withstudiocms/template-lang` es un lenguaje..." so it reads "...TypeScript
ESM e licencia MIT para plantillas..." (ensure only the conjunction before
"integración" is changed).
---
Nitpick comments:
In `@src/content/docs/es/ecosystem/packages/template-lang.mdx`:
- Line 46: The phrase "para interpolación de variables simple" misplaces the
adjective so it appears to modify "variables"; update the sentence in the text
that currently reads "A diferencia de otros lenguajes de plantillas, el lenguaje
de plantillas de StudioCMS se enfoca en la simplicidad y no incluye lógica
compleja o estructuras de control. Está principalmente diseñado para
interpolación de variables simple." to place "simple" next to "interpolación"
(for example: "Está principalmente diseñado para la interpolación simple de
variables" or "Está principalmente diseñado para la interpolación de variables
de forma simple") so the adjective clearly modifies "interpolación."
Adammatthiesen
approved these changes
Feb 21, 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
Translates docs in
ecosystem/packagesdirectorySummary by CodeRabbit