i18n(es): update index.mdx

[dreyfus92]

Description

• What does this PR change? Give us a brief description.
  Updates index.mdx

Summary by CodeRabbit

• Documentation
  • Updated all inline Markdown links to reference-style links for improved consistency and maintainability.
  • Corrected the "Variables de entorno" link to point to the appropriate page.
  • No changes to documentation content beyond link formatting.

[coderabbitai]

Walkthrough

The documentation file for the Spanish index page was updated to replace all inline Markdown links with reference-style links. This involved converting direct URL links within the content to use bracketed reference labels, and adding corresponding reference definitions at the end of the file. One link to the "Variables de entorno" page was corrected to point to the appropriate reference. No other content or logic was modified.

Changes

File(s)	Change Summary
src/content/docs/es/index.mdx	Converted all inline Markdown links to reference-style links; added reference definitions; corrected one link reference.

Possibly related PRs

• i18n(es): update multiple files pt. 2 #30: Both PRs update Spanish documentation files by converting direct Markdown links to reference-style links, making their changes related.
• i18n(es): multiple updates pt.3 #31: Both PRs focus on converting inline Markdown links to reference-style links in Spanish documentation files, directly modifying link formatting and adding reference definitions for improved consistency.
• i18n(es): more updates #29: Both PRs focus on converting inline Markdown links to reference-style links in Spanish documentation files, making their changes directly related.

Suggested labels

i18n

Suggested reviewers

• Adammatthiesen

---

📜 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 78c79b1 and 890f16a.

📒 Files selected for processing (1)

• src/content/docs/es/index.mdx (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/content/docs/es/index.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 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/index.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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b313ae1 and 78c79b1.

📒 Files selected for processing (1)

• src/content/docs/es/index.mdx (2 hunks)

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

• GitHub Check: Run Starlight Link Check

🔇 Additional comments (5)

src/content/docs/es/index.mdx (5)

48-52: Inline reference syntax conversion is correct
The move from inline Markdown to reference-style links for these calls is properly applied.

---

58-62: Reference-style links in the “Aprende sobre StudioCMS” ListCard are correct
The list uses reference-style links consistently and retains the intended targets.

---

65-69: Reference-style links in the “Customizing StudioCMS” ListCard are correct
All references and labels match their definitions and look good.

---

86-88: Closing <Center> component and reference comment placement
The closing tag for <Center> and the {/* Page MD Links */} comment correctly mark the start of the reference definitions.

---

90-97: Other reference definitions look correct
The remaining reference-style link definitions correctly map labels to their intended URLs.