Skip to content

i18n(es): update /package-catalog/#112

Merged
dreyfus92 merged 1 commit into
mainfrom
es-05
Apr 21, 2025
Merged

i18n(es): update /package-catalog/#112
dreyfus92 merged 1 commit into
mainfrom
es-05

Conversation

@dreyfus92
Copy link
Copy Markdown
Member

@dreyfus92 dreyfus92 commented Apr 21, 2025 •
edited by coderabbitai Bot
Loading

Description

  • What does this PR change? Give us a brief description.
    Updates /package-catalog/

Summary by CodeRabbit

  • Documentation
    • Added an explanation about the "Experimental" badge for plugins, clarifying its meaning and implications.
    • Updated installation instructions for several plugins to display more explicit package manager commands.
    • Modified code snippet annotations in configuration examples for improved clarity in documentation.

@dreyfus92 dreyfus92 requested a review from a team as a code owner April 21, 2025 01:32
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 21, 2025 •
edited
Loading

Walkthrough

This update modifies the Spanish documentation for the StudioCMS package catalog and its plugins. It adds a clarification about the "Experimental" badge to the main catalog page, explaining its meaning and implications. For the plugin documentation pages (studiocms-blog, studiocms-markdoc, studiocms-mdx), the installation instructions are updated to use a more explicit command structure in the <PackageManagers> component, and the code block annotations for configuration examples are adjusted to change how lines are highlighted or annotated.

Changes

Files Change Summary
src/content/docs/es/package-catalog/index.mdx Added an explanatory paragraph about the "Experimental" badge for plugins.
src/content/docs/es/package-catalog/studiocms-plugins/studiocms-blog.mdx
src/content/docs/es/package-catalog/studiocms-plugins/studiocms-markdoc.mdx
src/content/docs/es/package-catalog/studiocms-plugins/studiocms-mdx.mdx		 Updated <PackageManagers> usage to a more explicit command format and modified code block annotations for configuration examples.

Possibly related PRs

Suggested labels

i18n

Suggested reviewers

  • Adammatthiesen

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

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
🪧 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
Copy link
Copy Markdown
Member

studiocms-no-reply commented Apr 21, 2025

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/index.mdx Localization changed, will be marked as complete.
es/package-catalog/studiocms-plugins/studiocms-blog.mdx Localization changed, will be marked as complete.
es/package-catalog/studiocms-plugins/studiocms-markdoc.mdx Localization changed, will be marked as complete.
es/package-catalog/studiocms-plugins/studiocms-mdx.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[bot]
coderabbitai Bot reviewed Apr 21, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/content/docs/es/package-catalog/index.mdx (1)

14-14: Excelente adición de la aclaración sobre la etiqueta “Experimental”

La nueva línea ayuda a los usuarios a comprender el estado y las implicaciones de usar paquetes en desarrollo temprano.
[Sólo comentario de estilo] Se sugiere agregar una coma antes de “lo que significa” para mejorar la legibilidad y, por consistencia, cambiar “complementos” por “paquetes” en esta sección:

-Los complementos también pueden estar etiquetados como <Badge text="Experimental" variant="danger" /> lo que significa…
+Los paquetes también pueden estar etiquetados como <Badge text="Experimental" variant="danger" />, lo que significa…
🧰 Tools
🪛 LanguageTool

[uncategorized] ~14-~14: Probablemente falta un signo de puntuación.
Context: ...s también pueden estar etiquetados como lo que significa que el complemento aún...

(AI_ES_GGEC_MISSING_PUNCTUATION)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 78fcfe6 and 989fa77.

📒 Files selected for processing (4)
  • src/content/docs/es/package-catalog/index.mdx (1 hunks)
  • src/content/docs/es/package-catalog/studiocms-plugins/studiocms-blog.mdx (1 hunks)
  • src/content/docs/es/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1 hunks)
  • src/content/docs/es/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/es/package-catalog/index.mdx

[uncategorized] ~14-~14: Probablemente falta un signo de puntuación.
Context: ...s también pueden estar etiquetados como lo que significa que el complemento aún...

(AI_ES_GGEC_MISSING_PUNCTUATION)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run Starlight Link Check
🔇 Additional comments (6)
src/content/docs/es/package-catalog/studiocms-plugins/studiocms-blog.mdx (2)

24-24: Instalación más explícita con <PackageManagers>

La actualización para especificar pkg="studiocms", type='run' y args='add @studiocms/blog' mejora la claridad y uniformidad con el resto de la documentación de plugins.

28-28: Verificar el resaltado de líneas en el snippet

Se eliminó el prefijo ins= y se dejó {2, 6}, lo cual parece correcto. Por favor, confirma que la nueva sintaxis sigue resaltando las líneas 2 y 6 como se espera.

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

24-24: Actualización coherente del comando de instalación

El <PackageManagers> ahora indica explícitamente pkg="studiocms", type='run' y args='add @studiocms/mdx', alineándose con otros plugins.

28-28: Confirmar el comportamiento del fragmento de código

La eliminación de ins= por {2, 6} parece adecuada. Asegúrate de que esta nueva notación siga aplicando el resaltado en las líneas previstas.

src/content/docs/es/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (2)

24-24: Mejora de la instrucción de instalación

El componente <PackageManagers> ahora usa pkg="studiocms", type='run' y args='add @studiocms/markdoc', lo que clarifica el proceso de instalación.

28-28: Revisar la sintaxis de las líneas resaltadas

Se cambió ins={2, 6} por {2, 6}. Comprueba que las líneas 2 y 6 sigan resaltándose correctamente en el snippet.

@dreyfus92 dreyfus92 merged commit b9fa364 into main Apr 21, 2025
8 checks passed
@dreyfus92 dreyfus92 deleted the es-05 branch April 21, 2025 01:43
This was referenced Apr 21, 2025
Merged
Merged
This was referenced Feb 18, 2026
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Adammatthiesen Adammatthiesen Adammatthiesen approved these changes

@coderabbitai coderabbitai[bot] coderabbitai[bot] approved these changes

Assignees

No one assigned

Labels

i18n

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dreyfus92 @studiocms-no-reply @Adammatthiesen