i18n(es): update config-reference/index.mdx, translations.mdx & sqld-server.mdx

[dreyfus92]

Description

• What does this PR change? Give us a brief description.
  Updates multiple files

Summary by CodeRabbit

• Documentation
  • Updated Spanish configuration reference: introduced db, storageManager, logLevel, locale and features sections; removed several deprecated fields; refined default config and updated component example paths to use relative notation.
  • Corrected translation guide storage path and English translation filename reference.
  • Clarified Spanish database guide: simplified JWT generation example, specified Base64URL token format, corrected env hint localization, and made minor formatting improvements.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates Spanish docs: it revises the config reference to replace deprecated fields with new public config entries (db, storageManager, logLevel, locale, features), adjusts component example paths, updates translation file paths, and refines JWT commands and wording in the SQLd guide.

Changes

Cohort / File(s)	Summary
Config reference (Spanish) src/content/docs/es/config-reference/index.mdx	Replaces dateLocale: string with db: {} in default config, adds logLevel, storageManager, locale, and features; removes deprecated public fields (overrides, imageService, defaultFrontEndConfig, dashboardConfig, includedIntegrations, dateTimeFormat, sdk, pageTypeOptions); updates componentRegistry example path to ./src/components/MyComponent.astro and adds tableOfContents metadata.
Contributing — translations (Spanish) src/content/docs/es/guides/contributing/translations.mdx	Updates translation storage path from packages/studiocms/src/lib/i18n/translations to packages/studiocms/src/virtuals/i18n/translations and renames en-us.json → en.json.
Database — SQLd guide (Spanish) src/content/docs/es/guides/database/sqld-server.mdx	Reformats key-generation command into a fenced bash block, removes -c "iss=admin" arg, clarifies JWT is Base64URL-encoded and adjusts validity wording, localizes the SQLD env hint, and fixes minor spacing/newline artifacts.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• i18n(fr): update config-reference #147: Mirrors config-reference removals/additions (locale/features/logLevel/db) across locale docs.
• i18n(es): multiple files updates #24: Updates the Spanish config-reference and removes similar deprecated fields.
• i18n(es): translate sqld-server.mdx #114: Edits the same Spanish sqld-server.mdx guide (JWT/key instructions and formatting).

Suggested reviewers

• Adammatthiesen
• louisescher

Poem

🐇
I hopped through docs with nibbling cheer,
Trimmed old fields and brought new ones near.
Paths fixed, JWTs made neat,
Locales set — a tidy feat! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes—updating three Spanish localization files—and clearly identifies the specific files modified in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch es/update-002

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[htg-1-studiocms-cloud]

Dokploy Preview Deployment

Name	Status	Preview	Updated (UTC)
StudioCMS Docs	❌ Failed	Preview URL	2026-02-18T16:26:54.913Z

[studiocms-no-reply]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
es/config-reference/index.mdx	Localization changed, will be marked as complete.
es/guides/contributing/translations.mdx	Localization changed, will be marked as complete.
es/guides/database/sqld-server.mdx	Localization changed, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/content/docs/es/guides/contributing/translations.mdx (1)

38-38: ⚠️ Potential issue | 🟡 Minor

Update stale GitHub link to i18n configuration after lib/i18n → virtuals/i18n reorganization.

Line 38 links to the old path packages/studiocms/src/lib/i18n/index.ts#L8. The English source documentation does not include this link; it references the translations directory at packages/studiocms/src/virtuals/i18n/translations/ instead. Remove the hardcoded link or update it to match the English version for consistency.

Proposed fix (align with English source)

-Una vez que se hayan agregado las traducciones, se añadirán a la [configuración i18n de StudioCMS](https://github.com/withstudiocms/studiocms/blob/main/packages/studiocms/src/lib/i18n/index.ts#L8) y estarán disponibles en la próxima versión.
+Una vez que se hayan agregado las traducciones, se sincronizarán automáticamente y estarán disponibles en la próxima versión.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/es/guides/contributing/translations.mdx` at line 38, The
paragraph contains a stale GitHub link pointing to
packages/studiocms/src/lib/i18n/index.ts#L8; update or remove this hardcoded
link so it matches the English source which references
packages/studiocms/src/virtuals/i18n/translations/, or simply remove the link
entirely; edit the string containing the URL in translations.mdx (the sentence
beginning "Una vez que se hayan agregado las traducciones, se añadirán a la
[configuración i18n de StudioCMS]") to use the new virtuals/i18n/translations
path or no link for consistency.

🧹 Nitpick comments (1)

src/content/docs/es/config-reference/index.mdx (1)

172-173: Update these links to /es/ once Spanish translations of locale and features config pages are created.

The Spanish versions of locale.mdx and features.mdx do not yet exist in /es/config-reference/, so the current fallback to /en/config-reference/locale/ and /en/config-reference/features/ on lines 172–173 is acceptable. However, when these Spanish translations are completed, update the reference links to point to their Spanish counterparts.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/es/config-reference/index.mdx` around lines 172 - 173,
Update the two link reference entries [locale] and [features] so they point to
the Spanish pages once translations exist: change the target values currently
set to /en/config-reference/locale/ and /en/config-reference/features/ to
/es/config-reference/locale/ and /es/config-reference/features/ respectively;
locate the two reference lines named [locale] and [features] in
src/content/docs/es/config-reference/index.mdx and update their paths when the
Spanish locale.mdx and features.mdx files are added.

🤖 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/database/sqld-server.mdx`:
- Line 107: Update the `.env` comment for SQLD_AUTH_JWT_KEY to use the same
encoding term as line 107: change the phrase "codificado en base64" to
"Base64URL codificado" so both references to SQLD_AUTH_JWT_KEY consistently
indicate Base64URL encoding.

---

Outside diff comments:
In `@src/content/docs/es/guides/contributing/translations.mdx`:
- Line 38: The paragraph contains a stale GitHub link pointing to
packages/studiocms/src/lib/i18n/index.ts#L8; update or remove this hardcoded
link so it matches the English source which references
packages/studiocms/src/virtuals/i18n/translations/, or simply remove the link
entirely; edit the string containing the URL in translations.mdx (the sentence
beginning "Una vez que se hayan agregado las traducciones, se añadirán a la
[configuración i18n de StudioCMS]") to use the new virtuals/i18n/translations
path or no link for consistency.

---

Nitpick comments:
In `@src/content/docs/es/config-reference/index.mdx`:
- Around line 172-173: Update the two link reference entries [locale] and
[features] so they point to the Spanish pages once translations exist: change
the target values currently set to /en/config-reference/locale/ and
/en/config-reference/features/ to /es/config-reference/locale/ and
/es/config-reference/features/ respectively; locate the two reference lines
named [locale] and [features] in src/content/docs/es/config-reference/index.mdx
and update their paths when the Spanish locale.mdx and features.mdx files are
added.

[Adammatthiesen]

Check Link validation CI, and corabbitai comment

[coderabbitai]

🧹 Nitpick comments (1)

src/content/docs/es/config-reference/index.mdx (1)

70-70: Nitpick: use reflexive passive for consistency with the rest of the document.

Every other section description uses se utiliza / se usa (e.g., `db` es un objeto que se utiliza…, `verbose` es un booleano que se utiliza…). `storageManager` es usado… is the only outlier using the direct passive form.

✏️ Proposed fix

-`storageManager` es usado para configurar el plugin de administración de almacenamiento para StudioCMS.
+`storageManager` se usa para configurar el plugin de administración de almacenamiento para StudioCMS.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/es/config-reference/index.mdx` at line 70, Change the
wording for the `storageManager` description to use the reflexive passive to
match the rest of the doc: replace "`storageManager` es usado para configurar el
plugin de administración de almacenamiento para StudioCMS." with a reflexive
passive phrasing such as "`storageManager` se utiliza para configurar el plugin
de administración de almacenamiento para StudioCMS." to match other entries like
`db` and `verbose`.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/content/docs/es/config-reference/index.mdx`:
- Line 70: Change the wording for the `storageManager` description to use the
reflexive passive to match the rest of the doc: replace "`storageManager` es
usado para configurar el plugin de administración de almacenamiento para
StudioCMS." with a reflexive passive phrasing such as "`storageManager` se
utiliza para configurar el plugin de administración de almacenamiento para
StudioCMS." to match other entries like `db` and `verbose`.

[coderabbitai]

🤖 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/guides/database/sqld-server.mdx`:
- Line 63: Update the comment on the ASTRO_DB_APP_TOKEN env entry to use the
same encoding terminology as line 57: replace "codificado en base64" with
"codificado en base64URL" (or "base64URLEncoded") so both references describe
the same JWT format; locate the ASTRO_DB_APP_TOKEN comment in the docs (the line
that currently reads "pega tu token JWT codificado en base64 aquí") and make the
wording consistent with the earlier "base64URLEncoded" phrasing.