Skip to content

i18n(es): add 0-1-0-beta-17#132

Merged
Adammatthiesen merged 1 commit into
mainfrom
es-02
Apr 29, 2025
Merged

i18n(es): add 0-1-0-beta-17#132
Adammatthiesen merged 1 commit into
mainfrom
es-02

Conversation

@dreyfus92
Copy link
Copy Markdown
Member

@dreyfus92 dreyfus92 commented Apr 29, 2025

Description

  • What does this PR change? Give us a brief description.
    Translates 0-1-0-beta-17 to spanish

Summary by CodeRabbit

  • Documentation
    • Added a new page detailing the StudioCMS update to version 0.1.0-beta.17, including an overview of optimizations, bug fixes, new features like a comment system in the control panel, and important upgrade notes regarding password hashing algorithm changes.

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

coderabbitai Bot commented Apr 29, 2025

Walkthrough

A new Spanish-language documentation page has been added to describe the changes in StudioCMS version 0.1.0-beta.17. The page outlines performance optimizations, bug fixes, and new features such as a comment system in the control panel. It also includes a notice about a password hashing algorithm change introduced in the previous beta, advising users to update their passwords. No major code changes are present; the update is focused on documentation for the upgrade process.

Changes

File(s) Change Summary
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx Added a new Spanish documentation page detailing the StudioCMS 0.1.0-beta.17 update, features, fixes, and upgrade notes.

Possibly related PRs

Suggested labels

i18n

Suggested reviewers

  • Adammatthiesen

Poem

In burrows deep, I found a page anew,
Spanish words guiding what to do.
Upgrades and hashes, fixes in tow,
StudioCMS grows steady and slow.
With every doc, our warren expands—
Hopping forward, with guides in our hands!
🐇📄


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

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/upgrade/version-guides/0-1-0-beta-17.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.

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 (3)
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx (3)

2-4: Refine frontmatter description for clarity

The description field currently reads:

Actualiza StudioCMS a Beta.17

To improve clarity and consistency with other version guides, consider using the full version string and including "versión":

-description: Actualiza StudioCMS a Beta.17
+description: "Actualiza StudioCMS a la versión 0.1.0-beta.17"

13-13: Remove unused import

The ReadMore component is imported but not used in this file. To keep the code clean, please remove this line:

-import ReadMore from '~/components/ReadMore.astro'

27-27: Fix missing accent on "mejoró"

In Spanish, the past tense "mejoró" requires an accent on the "o". Please update:

-  - Se mejoro la detección de la ruta del archivo clave para el comando CLI [`crypto gen-jwt`](/es/how-it-works/cli/#crypto-gen-jwt).
+  - Se mejoró la detección de la ruta del archivo clave para el comando CLI [`crypto gen-jwt`](/es/how-it-works/cli/#crypto-gen-jwt).
🧰 Tools
🪛 LanguageTool

[misspelling] ~27-~27: Si el verbo está en pasado, se escribe con tilde.
Context: ...ieron problemas con Astro Fonts. - Se mejoro la detección de la ruta del archivo cla...

(SE_CREO)

📜 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 3a44a51.

📒 Files selected for processing (1)
  • src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx

[uncategorized] ~23-~23: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...ctualización - Nuevas características - Se añadió un nuevo sistema de comentario...

(AI_ES_GGEC_REPLACEMENT_OTHER)


[misspelling] ~27-~27: Si el verbo está en pasado, se escribe con tilde.
Context: ...ieron problemas con Astro Fonts. - Se mejoro la detección de la ruta del archivo cla...

(SE_CREO)


[uncategorized] ~28-~28: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...-works/cli/#crypto-gen-jwt). - Mejoras - Se reemplazó [lodash](https://www.npmjs....

(AI_ES_GGEC_REPLACEMENT_OTHER)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run Starlight Link Check
🔇 Additional comments (3)
src/content/docs/es/guides/upgrade/version-guides/0-1-0-beta-17.mdx (3)

17-17: Verify localization of QuickUpdate component

The <QuickUpdate /> component is included here, but please confirm that its internal copy is displayed in Spanish or that it pulls the correct locale data. If it defaults to English, you may need to add a Spanish version or adjust its props.


32-34: Ensure consistent tone in user-facing messaging

The aside uses informal second-person ("ten en cuenta", "te recomendamos") while other docs may adopt an impersonal or formal tone. Please verify the preferred style for Spanish documentation (e.g., impersonal "Recomendamos a los usuarios...") and adjust accordingly.


19-31: Great translation of update summary

The summary section and bullet points accurately reflect the original English content, and the terminology is consistent (e.g., "panel de control", "optimizado", "procesamiento de niveles de permisos"). No issues spotted apart from the missing accent mentioned above.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~23-~23: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...ctualización - Nuevas características - Se añadió un nuevo sistema de comentario...

(AI_ES_GGEC_REPLACEMENT_OTHER)


[misspelling] ~27-~27: Si el verbo está en pasado, se escribe con tilde.
Context: ...ieron problemas con Astro Fonts. - Se mejoro la detección de la ruta del archivo cla...

(SE_CREO)


[uncategorized] ~28-~28: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...-works/cli/#crypto-gen-jwt). - Mejoras - Se reemplazó [lodash](https://www.npmjs....

(AI_ES_GGEC_REPLACEMENT_OTHER)

@Adammatthiesen Adammatthiesen merged commit 592967f into main Apr 29, 2025
8 checks passed
@Adammatthiesen Adammatthiesen deleted the es-02 branch April 29, 2025 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants