i18n(es): update translations, 0-1-0-beta.16 & cli

[dreyfus92]

Description

• What does this PR change? Give us a brief description.
  Updates translations, 0-1-0-beta.16 & cli

Summary by CodeRabbit

• Documentation
  • Removed "badge" indicators from the sidebar metadata in several Spanish documentation pages. No other content was changed.

[coderabbitai]

Walkthrough

This update removes the "badge" property from the sidebar configuration in the frontmatter of three Spanish documentation files. The affected files are related to contributing translations, CLI usage, and a version upgrade guide. Only the badge metadata is deleted; no other content, logic, or structure within the documents is changed.

Changes

Files	Change Summary
src/content/docs/es/guides/contributing/translations.mdx src/content/docs/es/how-it-works/cli.mdx src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-16.mdx	Removed the "badge" property from the sidebar metadata in the frontmatter of each file. No other changes made.

Possibly related PRs

• i18n(es): update translations.mdx #108: Modifies the badge text and content in the same translations.mdx file, showing both PRs alter sidebar badge metadata but with opposite intentions.
• i18n(de): translate beta.17 #129: Removes the "badge" property from German documentation files, analogous to this PR's changes in Spanish docs.
• update docs for beta17 #127: Removes the "badge" property from the English originals of the same documentation files affected in this PR.

Suggested labels

i18n

Suggested reviewers

• Adammatthiesen

Poem

Three little badges, green and bright,
Hopped away in the documentation night.
Sidebar simpler, metadata trimmed,
The Spanish docs now neatly brimmed.
A rabbit winks with gentle cheer—
Clean frontmatter, spring is here!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 64ac272 and 7b833ae.

📒 Files selected for processing (3)

• src/content/docs/es/guides/contributing/translations.mdx (0 hunks)
• src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-16.mdx (0 hunks)
• src/content/docs/es/how-it-works/cli.mdx (0 hunks)

💤 Files with no reviewable changes (3)

• src/content/docs/es/how-it-works/cli.mdx
• src/content/docs/es/guides/contributing/translations.mdx
• src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-16.mdx

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Run Starlight Link Check

---

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

🪧 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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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/guides/contributing/translations.mdx	Localization changed, will be marked as complete.
es/guides/upgrade/version-guides/0-1-0-beta-16.mdx	Localization changed, will be marked as complete.
es/how-it-works/cli.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.