Conversation
Dokploy Preview Deployment
|
Contributor
📝 WalkthroughWalkthroughAdds four new Spanish documentation pages: ecosystem overview, custom-frontend rendering guide, Effect integration, and S3 storage configuration with provider-specific environment examples. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Member
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
src/content/docs/es/package-catalog/storage-managers/s3-storage.mdx (1)
50-128: Trailing spaces on all provider section headings.Lines 50, 63, 76, 89, 102, 115, and 128 each have a trailing space after the heading text (e.g.
### AWS ␣). No rendering impact, but worth cleaning up for consistency.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/es/package-catalog/storage-managers/s3-storage.mdx` around lines 50 - 128, Remove the trailing spaces after each provider heading (e.g., the headings "### AWS", "### Cloudflare R2", "### DigitalOcean Spaces", "### Backblaze B2", "### MinIO", "### Wasabi", and "### Linode Object Storage") so the headings end immediately after the provider name; edit the MDX file and trim the trailing whitespace for those heading lines to ensure consistent formatting.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/es/ecosystem/index.mdx`:
- Line 8: Replace three Spanish grammar issues in the document: change the
phrase "plugins y integraciones" to "plugins e integraciones" (use "e" before
the "i" sound), replace "pre-construidos" with "preconstruidos" (remove the
unnecessary hyphen), and insert a comma in the contrastive clause changing
"datos pero también" to "datos, pero también".
- Around line 1-4: The frontmatter for this page is missing the i18n flag; add
i18nReady: true to the YAML frontmatter at the top (alongside title: Vista
general del ecosistema and topic: ecosystem) so the i18n tracking system marks
this page as translated; ensure the new key is placed within the existing
triple-dashed frontmatter block.
In `@src/content/docs/es/how-it-works/effect.mdx`:
- Around line 19-25: Add three small Spanish grammar fixes in the paragraph
containing "la siguiente exportación": insert a colon after "la siguiente
exportación" so it reads "la siguiente exportación:", change "del exportación"
to the correct feminine form "de la exportación", and add a comma before "así
como" so the sentence has ", así como" after the quoted code fragment `import {}
from 'effect';`. Ensure the punctuation and article changes are applied in the
same sentence that mentions the StudioCMS export and the example code block.
---
Nitpick comments:
In `@src/content/docs/es/package-catalog/storage-managers/s3-storage.mdx`:
- Around line 50-128: Remove the trailing spaces after each provider heading
(e.g., the headings "### AWS", "### Cloudflare R2", "### DigitalOcean Spaces",
"### Backblaze B2", "### MinIO", "### Wasabi", and "### Linode Object Storage")
so the headings end immediately after the provider name; edit the MDX file and
trim the trailing whitespace for those heading lines to ensure consistent
formatting.
Contributor
There was a problem hiding this comment.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@src/content/docs/es/ecosystem/index.mdx`:
- Line 30: Replace the misplaced comma in the sentence containing
`@withstudiocms/kysely` by moving the comma from after "pero" to before it —
change "datos pero, también" to "datos, pero también" so the contrastive clause
is punctuated correctly.
- Around line 1-4: The frontmatter at the top of the document is missing the
i18nReady flag; add the line i18nReady: true into the YAML frontmatter (between
the existing --- markers), e.g., alongside title/topic entries so the
frontmatter includes i18nReady: true as a boolean value to ensure the i18n
tracking system marks this page complete.
In `@src/content/docs/es/how-it-works/effect.mdx`:
- Around line 19-25: Two grammar fixes: add a colon after "la siguiente
exportación" and insert a comma before "así como" in the sentence that follows
the code block (the sentence referencing `'effect';`); update the text around
the export example (the line containing "la siguiente exportación" and the
subsequent sentence referencing "import { Effect, Context, Schema, Data } from
'studiocms/effect';" and "'effect'; así como") to read "la siguiente
exportación:" and "'effect';, así como" respectively.
Adammatthiesen
approved these changes
Feb 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds the following translations:
ecosystem/index.mdx,rendering.mdx,effect.mdx&s3-storage.mdxSummary by CodeRabbit