i18n(es): more updates

[dreyfus92]

Description

• What does this PR change? Give us a brief description.
  adds more updated files from spanish docs

Summary by CodeRabbit

• Documentation
  • Improved hyperlink formats across several guides for enhanced readability.
  • Updated translation management content to reflect the switch to a new service with an updated badge.
  • Revised pages with added guidance on prerequisites and OAuth authentication configurations.
• Style
  • Applied minor formatting adjustments for consistency in the documentation.

[coderabbitai]

Walkthrough

This pull request updates several Spanish documentation files. The changes primarily replace inline URLs with reference-style links, add corresponding reference declarations, update the translation resource from Weblate to Crowdin, adjust formatting details, and clarify prerequisites such as the required Node.js version. These modifications are purely textual and improve consistency and maintainability in the documentation.

Changes

File(s)	Change Summary
src/.../contributing/code-contributions.mdx, src/.../how-it-works/cli.mdx, src/.../start-here/getting-started.mdx	Replaced inline URLs with reference-style links; added corresponding link reference declarations; added Node.js version requirement notice in the getting-started file.
src/.../contributing/translations.mdx	Updated image link and text to replace the Weblate widget with a Crowdin badge and guide.
src/.../how-it-works/index.mdx	Removed an extraneous newline from the StudioCMS rendering endpoint description.

Suggested labels

i18n

Suggested reviewers

• Adammatthiesen

Poem

I'm a rabbit with hops so bright,
Document changes make my day light.
Links now reference with style and grace,
Formatting refined in every place.
I twitch my nose and celebrate with cheer,
Hopping through docs with joy so clear! 🐇✨

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[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/contributing/code-contributions.mdx	Localization changed, will be marked as complete.
es/contributing/translations.mdx	Localization changed, will be marked as complete.
es/how-it-works/cli.mdx	Localization changed, will be marked as complete.
es/how-it-works/index.mdx	Localization changed, will be marked as complete.
es/start-here/getting-started.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: 0

🧹 Nitpick comments (3)

src/content/docs/es/how-it-works/cli.mdx (1)

212-212: Consider Consistent Capitalization in Link Text
In the ReadMore component, the link text "[documentación de Variables de Entorno]" uses capital letters for “Variables” and “Entorno.” Ensure that this styling is consistent with the rest of the documentation. If your style guide prefers a different casing, consider updating accordingly.

🧰 Tools

🪛 LanguageTool

[typographical] ~212-~212: Mayúsculas y minúsculas recomendadas.
Context: ... entorno, consulta la [documentación de Variables de Entorno][environment-variables].</Re...

(AI_ES_GGEC_REPLACEMENT_CASING_UPPERCASE)

src/content/docs/es/start-here/getting-started.mdx (2)

71-71: Potential Redundancy in ReadMore Sections
There are two separate ReadMore blocks linking to [db-url-token]. Verify whether both instances are necessary or if consolidating the information might improve clarity and avoid potential redundancy.

---

310-310: Consider a Spanish Alternative for “Plugins”
The term “plugins” is used in the line referencing the [Catálogo de Paquetes]. Depending on the target audience and the project’s style guidelines, consider using a Spanish alternative like “complementos” to enhance the localization.

🧰 Tools

🪛 LanguageTool

[style] ~310-~310: Considere alternativas para este anglicismo (recomendable sobre todo en contextos más formales).
Context: ...a construido, puedes consultar nuestros plugins en el [Catálogo de Paquetes][package-ca...

(ES_SIMPLE_REPLACE_ANGLICISM_PREMIUM_PLUGINS)

---

[misspelling] ~310-~310: El pronombre personal «él» lleva tilde.
Context: ...o, puedes consultar nuestros plugins en el [Catálogo de Paquetes][package-catalog]...

(EL_TILDE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 91ca02a and e21b3d2.

📒 Files selected for processing (5)

• src/content/docs/es/contributing/code-contributions.mdx (1 hunks)
• src/content/docs/es/contributing/translations.mdx (1 hunks)
• src/content/docs/es/how-it-works/cli.mdx (1 hunks)
• src/content/docs/es/how-it-works/index.mdx (1 hunks)
• src/content/docs/es/start-here/getting-started.mdx (7 hunks)

🧰 Additional context used

🪛 LanguageTool

src/content/docs/es/start-here/getting-started.mdx

[style] ~310-~310: Considere alternativas para este anglicismo (recomendable sobre todo en contextos más formales).
Context: ...a construido, puedes consultar nuestros plugins en el [Catálogo de Paquetes][package-ca...

(ES_SIMPLE_REPLACE_ANGLICISM_PREMIUM_PLUGINS)

---

[misspelling] ~310-~310: El pronombre personal «él» lleva tilde.
Context: ...o, puedes consultar nuestros plugins en el [Catálogo de Paquetes][package-catalog]...

(EL_TILDE)

src/content/docs/es/how-it-works/cli.mdx

[typographical] ~212-~212: Mayúsculas y minúsculas recomendadas.
Context: ... entorno, consulta la [documentación de Variables de Entorno][environment-variables].</Re...

(AI_ES_GGEC_REPLACEMENT_CASING_UPPERCASE)

🔇 Additional comments (7)

src/content/docs/es/how-it-works/index.mdx (1)

134-134: Minor Formatting Adjustment in the Renderer Endpoint Description
The newline removed at the end of the /studiocms_api/renderer/render endpoint description is a purely cosmetic change that helps tighten the Markdown formatting. Please double-check that this change does not affect readability in any Markdown renderers used by the project.

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

20-20: Updated Translation Status Badge Link
The image source for the translation status badge has been updated to point to the Crowdin resource. This change clearly reflects the switch from the old translation management platform to Crowdin and improves consistency in branding.

src/content/docs/es/contributing/code-contributions.mdx (1)

60-63: Refactored Contributor Link Format
Converting the direct URL to a reference-style link for the contributors list improves maintainability and consistency across the documentation. Please verify that the reference [contributors] correctly resolves to /es/contributing/getting-started/#nuestros-contribuyentes.

src/content/docs/es/how-it-works/cli.mdx (1)

212-217: Standardized Environment Variables Link
Replacing the inline URL with a reference-style link for the environment variables documentation enhances maintainability. The newly added reference [environment-variables] (along with [templates]) should be verified for correctness and consistency with similar links in other files.

🧰 Tools

🪛 LanguageTool

[typographical] ~212-~212: Mayúsculas y minúsculas recomendadas.
Context: ... entorno, consulta la [documentación de Variables de Entorno][environment-variables].</Re...

(AI_ES_GGEC_REPLACEMENT_CASING_UPPERCASE)

src/content/docs/es/start-here/getting-started.mdx (3)

19-22: Clarification on Prerequisites
The updated prerequisites now clearly specify the required Node.js version supported by Astro and note that Bun and Deno are not compatible. This clarification helps set proper expectations for new users.

---

30-30: Consistent Reference for Database Credentials
The ReadMore block that directs users to "[URL de la base de datos y token para @astrojs/db][db-url-token]" replaces a direct URL with a reference link. This approach improves consistency and centralizes link management.

---

358-365: Introduction of Reference Links for Enhanced Maintainability
The addition of multiple reference links—such as [package-catalog], [environment-variables], [config-reference], [db-url-token], [encryption-key], [oauth-environment-variables], and [auth-config-ref]—significantly improves the document’s maintainability by centralizing link targets. Please confirm that each reference correctly points to its intended destination.