i18n(es): translate studiocms-wysiwyg.mdx

[dreyfus92]

Description

• What does this PR change? Give us a brief description.
  Translates studiocms-wysiwyg.mdx

Summary by CodeRabbit

• Documentation
  • Added new Spanish-language documentation for the WYSIWYG editor integration in StudioCMS, including introduction and installation instructions.

[coderabbitai]

Walkthrough

A new Spanish-language documentation file for the @studiocms/wysiwyg package has been added. This document introduces the package as an integration that provides a WYSIWYG editor for StudioCMS projects. It includes metadata, an experimental badge, a brief description, and installation instructions with a code example for updating the StudioCMS configuration. The file imports UI components for formatting and layout but does not cover further usage or configuration options.

Changes

File(s)	Change Summary
src/content/docs/es/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx	Added new Spanish documentation for @studiocms/wysiwyg with introduction and installation instructions, including metadata and experimental badge.

Possibly related PRs

• i18n(ko-KR): create studiocms-wysiwyg.mdx #99: Adds new localized documentation for the @studiocms/wysiwyg package in another language, focusing on installation and configuration.
• i18n(es): update /package-catalog/ #112: Updates Spanish package catalog docs with clarifications about the experimental badge and improves installation command formatting for plugins.

Suggested reviewers

• Adammatthiesen

---

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/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx	Localization added, 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 (5)

src/content/docs/es/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx (5)

6-6: Fix punctuation in the Spanish description

The description ends with both a period and an exclamation mark, which is redundant in Spanish. It should read:

- description: "¡Agrega un editor WYSIWYG a tu proyecto StudioCMS con facilidad.!"
+ description: "¡Agrega un editor WYSIWYG a tu proyecto StudioCMS con facilidad!"

---

9-9: Unify YAML quoting style

In the frontmatter, text: 'Experimental' uses single quotes, while other string values use double quotes. For consistency, consider:

-    text: 'Experimental'
+    text: "Experimental"

---

13-13: Add missing semicolon to import

The first import is missing a semicolon, causing an inconsistency with the second import. Please add it:

- import { PackageManagers } from 'starlight-package-managers'
+ import { PackageManagers } from 'starlight-package-managers';

---

24-24: Use consistent JSX attribute quoting

In the <PackageManagers> component, attributes mix single and double quotes. For consistency, switch to double quotes:

-    <PackageManagers pkg="studiocms" type='run' args='add @studiocms/wysiwyg' />
+    <PackageManagers pkg="studiocms" type="run" args="add @studiocms/wysiwyg" />

---

32-32: Align code snippet indentation

The export default line has an extra leading space, making the snippet misaligned. Consider:

-    export default defineStudioCMSConfig({
+   export default defineStudioCMSConfig({

This will align it with the import lines above and render nicely in the docs.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c3678b8 and 22917c0.

📒 Files selected for processing (1)

• src/content/docs/es/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx (1 hunks)

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

• GitHub Check: Run Starlight Link Check